We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Although yamljs output is valid from a kubectl point of view, the document format might be improved for a better "human reading experience".
e.g. this is an output generated automatically by kubectl, for a ingress with kube-lego:
apiVersion: extensions/v1beta1 kind: Ingress metadata: name: nginx namespace: default annotations: kubernetes.io/tls-acme: 'true' spec: rules: - http: paths: - path: / backend: serviceName: nginx servicePort: 80 host: nginx.minikube.sesispla.net tls: - hosts: - nginx.minikube.sesispla.net secretName: nginx-secret
And how a human might expect the document to be formatted:
apiVersion: extensions/v1beta1 kind: Ingress metadata: name: nginx namespace: default annotations: kubernetes.io/tls-acme: 'true' spec: rules: - host: nginx.minikube.sesispla.net http: paths: - path: / backend: serviceName: nginx servicePort: 80 tls: - hosts: - nginx.minikube.sesispla.net secretName: nginx-secret
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Although yamljs output is valid from a kubectl point of view, the document format might be improved for a better "human reading experience".
e.g. this is an output generated automatically by kubectl, for a ingress with kube-lego:
And how a human might expect the document to be formatted:
The text was updated successfully, but these errors were encountered: