Tool to generate Kubernetes architecture diagrams with Kubernetes icons set

[mkimuram]

It would be nice if we can automatically generate Kubernetes architecture diagrams with Kubernetes icons set from an actual Kubernetes deployment. To discuss this more in detail, I’ve implemented PoC code in https://github.com/mkimuram/k8sviz.

Any feedback is welcomed, but I expect feedback especially on:

• Whether we should have this kind of tools, in the first place,
• What kind of diagrams are needed to be generated,
• In which repo we should maintain this kind of tools,
• Should we rewrite the tool with a more maintainable programing language.

[mkimuram]

/sig architecture
@etiennecoutaud @cblecker @thockin @bgrant0607 @jdumars

Any feedback?

[micheelengronne]

Seems great. For threat modelling it would be of good use. +1

[cblecker]

While I can see the value in a tool to do this, I don't think this needs to or should be done by the upstream project. I think this is a great thing to have in the community though.

[aleksas]

+1

[freepirat11]

+10

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[micheelengronne]

/remove-lifecycle rotten

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sandipanpanda]

/reopen
/remove-lifecycle rotten

[k8s-ci-robot]

@sandipanpanda: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen
/remove-lifecycle rotten

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sandipanpanda]

/reopen
/lifecycle frozen

[k8s-ci-robot]

@sandipanpanda: Reopened this issue.

In response to this:

/reopen
/lifecycle frozen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[pom11]

Alternative https://github.com/mkimuram/k8sviz