-
Notifications
You must be signed in to change notification settings - Fork 238
Conversation
Oh wow, I was looking at #30 and added the "Help needed" label a few minutes ago :) Let us know what happens once you've got the additional gRPC logs with more detail about why the health checks fail. |
The health/liveness check error was my fault:
Copy and paste error when generating the server's key and cert 😀. |
OK, got kiam working on the Amazon EKS preview using this chart.
Rebased and squashed my previous commits, plus today's fixes, into a single commit. Next is to upgrade to the |
It looks like the only configuration change for v2.6 is the addition of the |
I'll update to v2.7 now that's the latest version. |
Updated to kiam v2.7.
|
@pingles Once you are happy I will submit the chart as an Incubator chart to https://github.com/kubernetes/charts and work on the items listed here. |
@ewbankkit cool, that'd be great, thanks! We don't use Helm so I'd be delighted if you'd like to pick up owning the Helm integration? 😄 |
Sure, why not. |
Work moved to helm/charts#5330. |
Thank you for contributing this! |
Addresses #30.
I did not address #29 and assume that the TLS certificates and private keys are stored as Kubernetes secrets as described in https://github.com/uswitch/kiam/blob/master/docs/TLS.md.
Based on the deployment YAMLs in https://github.com/uswitch/kiam/tree/master/deploy.
Still a WIP as I have not yet got kiam working in my environment - server health and liveness checks are failing; I still have to enable debugging as described in #17.