-
Notifications
You must be signed in to change notification settings - Fork 56
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
Simplify Helm install #492
Conversation
7c0ca0b
to
f7ecfd5
Compare
docs/destinations/kubernetes.md
Outdated
@@ -0,0 +1,44 @@ | |||
## Introduction |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love that you created the first of these!
4c0c147
to
dd8d861
Compare
README.md
Outdated
- kind: role | ||
name: viewer | ||
destinations: | ||
- name: <cluster name> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we can add a comment here to get the reader context around what the cluster name is
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that's initially why it set a static cluster name ("my-first-cluster"). I'm happy to add something if you have any suggestions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the name being left out like this for clarity. What do you think of something like this?
destinations:
- name: <cluster name> # the cluster name can be set on deploying a new engine, otherwise it will default to the name of the cluster that the engine is running in
Are the empty |
@@ -0,0 +1,34 @@ | |||
************************************************* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work on this!
no, they originally had content but it's no longer necessary |
aaad674
to
3e6d8ab
Compare
47b16bd
to
1a34888
Compare
8bf8a17
to
ac786a6
Compare
ac786a6
to
c970b62
Compare
24b89e1
to
e96ca51
Compare
README.md
Outdated
* [Destinations](./docs/destinations) | ||
* [Kubernetes](./docs/destinations/kubernetes.md) | ||
|
||
### Updating Infra |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit/optional thing: should we call this "Upgrading?"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Switched to Upgrade
instead since there's no other -ing
in this doc
7677e9e
to
5ab61b3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM – incredible work!
ca66a98
to
c340cc8
Compare
c340cc8
to
1c26a85
Compare
Two paradigm shifts are captured in this PR.
Auto-discover registry. If a registry host is not provided, the engine will try to query Kubernetes Services to find an appropriate host. This will use the new label
infrahq.com/flavor
to find a registry service.Both the registry and engine has been updated to accept URIs for secrets, right now root API key and engine API key. The services themselves will resolve this reference to actual values. Implementation will vary.
For now, the only support format is
file://
which will look for the secrets in the filesystem at the path provided. In the future, this can be used to get secrets from Vault, AWS KMS, whatever else.These changes combined allows a fully functional Infra deploy using a single
infra
Helm chart.TODO:
image.tag
,image.pullPolicy
, etc.Fixes #465
Fixes #484