I actually saw this in code review but then I noticed the old PNGs were also around 1-2 MB. Probably a little room for improvement if we pass these to online PNG optimizers. It seems like the main issue is that the resolution is simply too large.

In README.md there is the following command:

docker run --it  --name tgr -p 5000:5000 -e CLIENT_ID="xxxxxxx" -e CLIENT_SECRET="xxxxxxxxxxxxxxx" -e DEBUG="True" tgr

There is two issues with that:

1. It should be -it, rather than --it, since the first one is invalid
2. You also need to specify -e HOST="0.0.0.0" and -e PORT="5000" in order for the app to start.

Addi

Before creating a feature request, please search existing feature requests to see if you find a similar one. If there is a similar feature request please up-vote it and/or add your comments to it instead

Why do you want this feature?
When draining nodes on a production cluster, it might be safer to use a health check between node/nodegroup draining loops - to ensure that until now things

Describe the solution you'd like
It would be neat to see the start time of plugins when looking at sonobuoy status. For example, when E2E are running, they may take a while, but when did they start?

$ sonobuoy status                                                                                                            
PLUGIN		STATUS		COUNT
e2e		running		1
systemd_logs	comple

I'm submitting a...

• bug report
• feature request
• support request - read the FAQ first!
• kudos, thank you, warm fuzzy

What is the current behavior?

When I apply the EKS Spot Instance [example](https://github.com/terraform-aws-modules/terraform-aws-eks/tree/master/examples/spot_

similar to what's shown in screenshot here: https://github.com/so-fancy/diff-so-fancy#screenshot

With the switch to v1.10 in #70 we can now make use of kubernetes/kubernetes#55479 and set noTaintMaster: true in kubeadm.conf instead of untainting after initialisation.

Perhaps also depends on #71?

Hi,

Even if type and autocompletion done by IDE are great auto-documentation, It would be even nicer to have java doc. So when you require doc from your IDE you can have something better than:

Tx man

Works in Safari, Chrome for Mac, Chrome for PC, Edge, but not IE version 11.192.16299.0 on Windows 10

yaml.reader.ReaderError: unacceptable character #x1f48e: special characters are not allowed
in "", position 1195

This seems to come from the python yaml reader which incorrectly rejects special unicode characters.
The character in particular is 💎, which kubernetes gladly accepts as valid unicode.

https://www.compart.com/en/unicode/U+1F48E

Component:

'salt', 'kubectl-plugin', 'solutions'

Why this is needed:

Centralized CLI

What should be done:

MetalK8s get environment command of solution should be par

README.md grew large so it would be useful to structure the docs in a gh-pages based site.
We can use: jekyll, mkdocs or hugo as doc site generator

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Feature request

Version of Helm and Kubernetes:
All

Which chart:
Distribution

Description:
This is a feature request to add javaOpts.other to the distribution chart, just like there is in Artifactory. This is to be able to easily add java opts like to add a custom java keystore.

values.yaml:
javaOpts:
other:

Templat

Kubernaut curl API:

Claim a cluster:
 GET <URL>/claims/<client-supplied-globally-scoped-claim-name>?expires=<deadline> -> kubeconfig file

Renew a claim:
 GET <URL>/claims/<client-supplied-globally-scoped-claim-name>?expires=<new-later-deadline> -> kubeconfig file

Release a cluster
 GET <URL>/claims/<client-supplied-globally-scoped-claim-name>?expires=<time-in-past> -> kubeconfig f

It might be useful to document how to use this on an RBAC enabled cluster and how to create the service account, role, and role binding using the official kubernetes java client.

        ApiClient officialClient = Config.fromUserPassword(
                "https://la-de-do-da"
                 "username",
                 "password"
        );

        CoreV1Api coreV1Api = new CoreV1

The documentation shows CSE supports Photon OS 1.0, Rev 2, Photon OS 2.0 GA, and Ubuntu 16.04.4 LTS as the VM templates. Any roadmap to support more distro & verison, say RHEL 7.X and Ubuntu 18.04?