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

Expose Kuma rest api in read only mode #377

Merged
merged 1 commit into from
Oct 26, 2019

Conversation

sterchelen
Copy link

Summary

Expose kuma rest api in ro mode

Issues resolved

Fix #364

@sterchelen sterchelen force-pushed the feature/k8s-conf-rest-api branch 2 times, most recently from 4ea6673 to bae50bc Compare October 25, 2019 23:22
Ref kumahq#364

Signed-off-by: Nicolas Sterchele <sterchelen@gmail.com>
@yskopets yskopets self-assigned this Oct 26, 2019
Copy link
Contributor

@yskopets yskopets left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sterchelen Thanks a lot for your contribution!

@yskopets yskopets merged commit b5d2edb into kumahq:master Oct 26, 2019
@yskopets yskopets added this to the 0.3.0 milestone Oct 26, 2019
@sterchelen sterchelen deleted the feature/k8s-conf-rest-api branch October 27, 2019 08:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

update k8s configuration generated by kumactl install control-plane to expose Kuma REST API in read-only mode
2 participants