Skip to content
New issue

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

Improve yaml-js output format #6

Open
sesispla opened this issue Jul 11, 2017 · 0 comments
Open

Improve yaml-js output format #6

sesispla opened this issue Jul 11, 2017 · 0 comments

Comments

@sesispla
Copy link
Owner

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant