-
Notifications
You must be signed in to change notification settings - Fork 6
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
fix: Hacking on ironic component #10
fix: Hacking on ironic component #10
Conversation
9ebdf98
to
3cf8831
Compare
So unfortunately OpenStack Helm doesn't publish helm charts that can be consumed like | ||
regular helm charts. You must instead clone two of their git repos side by side and | ||
build the dependencies manually. They additionally don't split out secrets but instead | ||
template them into giant config files or even executable scripts that then get stored | ||
as secrets, a clear violation of <https://12factor.net>. As a result we cannot store | ||
a declarative config of Keystone and allow users to supply their own secrets. |
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.
Is it just because they don't publish them in a repo? If so, could we just host it ourselves internally?
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 certainly an option. I'm happy to get some ideas around it.
table: "*" | ||
username: ironic | ||
grantOption: true | ||
host: "%" |
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.
should we restrict this to pod networking subnet?
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.
Yeah that would make sense. No idea how to look that up.
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.
kubectl get nodes -o jsonpath='{.items[*].spec.podCIDR}'
would be one way, but it's also subject to change so maybe just 10.x.x.x would make sense
Closing this out in favor of #11 which integrates all of these changes. |
My changes to get it to progress the deployment. The ironic-api starts, but ironic-conductor fails to start: