-
Notifications
You must be signed in to change notification settings - Fork 313
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
[EKS] [Aggregation Layer]: Configure Aggregation Layer ('client-ca-file' ConfigMap missing) #152
Comments
@whereisaaron support for Aggregation and Admission controllers was added in September - https://aws.amazon.com/about-aws/whats-new/2018/10/amazon-eks-enables-support-for-kubernetes-dynamic-admission-cont/ The caveat is projects need to be running at least the 1.10+ Looks like Looks like Is this still an issue? |
Excellent. Thanks for the update and explanation @christopherhein I'll retest with these new versions. |
There is no release of |
Awesome, we’re you able to test with the canary release and validate? If so we should close this. @munnerz do you have an expected stable release date with that patch? |
I tested with the canary
|
Hey Aaron - that looks like an error unrelated to API aggregation - we've
got a troubleshooting guide that should help walk you through resolving it
😄
https://cert-manager.readthedocs.io/en/latest/getting-started/troubleshooting.html
I'll be cutting a new release early next week (hopefully Monday). My
vacation aligned badly with that PR being merged, hence the delay 🙈
…On Sun, 17 Feb 2019 at 04:12, Aaron Roydhouse ***@***.***> wrote:
I tested with the canary cert-manager release (ed0c86e
<https://quay.io/repository/jetstack/cert-manager-controller?tag=latest&tab=tags>),
but I still getting the webhook errors on EKS. Though it strangely works
fine on my GKE k8s v1.11 clusters. I guess GKE supports both the old and
new flow? It looks like cert-manager needs other changes for the new flow.
I0217 03:59:47.536290 1 controller.go:142] issuers controller: syncing item 'cert-manager/cert-manager-webhook-ca'
I0217 03:59:47.536377 1 setup.go:45] Error getting keypair for CA issuer: secret "cert-manager-webhook-ca" not found
I0217 03:59:47.536408 1 sync.go:72] Error initializing issuer: secret "cert-manager-webhook-ca" not found
E0217 03:59:47.536432 1 controller.go:144] issuers controller: Re-queuing item "cert-manager/cert-manager-webhook-ca" due to error processing: secret "cert-manager-webhook-ca" not found
Error from server (InternalError): error when creating "cluster-issuer.yaml": Internal error occurred: failed calling admission webhook "clusterissuers.admission.certmanager.k8s.io": the server is currently unable to handle the request
container "webhook" in pod "cert-manager-webhook-6756b488bb-g65t2" is waiting to start: ContainerCreating
Warning FailedMount 75s (x11 over 7m27s) kubelet, ip-172-21-49-10.ap-southeast-2.compute.internal MountVolume.SetUp failed for volume "certs" : secrets "cert-manager-webhook-webhook-tls" not found
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#152 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAMbP4X8IVngwKHiTI2Dm1J4bGRdONKHks5vONargaJpZM4akkJw>
.
|
I came across this issue while running Sonobuoy E2E tests as well. Here are the log details:
Other useful info:
Does Amazon not run the E2E Conformance tests? |
Tell us about your request
Support webhooks for the API Aggregation Layer by issue a creating the
client-ca-file
ConfigMap.How to configure the Aggregation Layer:
https://kubernetes.io/docs/tasks/access-kubernetes-api/configure-aggregation-layer/
See
--requestheader-client-ca-file
in https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/ (this is current version reference but this functionality has been available since at least v1.8.x)Which service(s) is this request for?
EKS (k8s v1.11.5)
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Trying to install
cert-manager
with webhook CRD validation. Installation fails because EKS appears not to be k8s conformant in this regard.Trying to install Prometheus on EKS but again Aggregation Layer has not been properly configured in the EKS control plane.
Are you currently working around this issue?
Disabling Aggregation Layer functionality where possible.
Additional context
The Aggregation Layer with webhooks has been available since k8s v1.8.x or earlier.
This works out of the box on
kube-aws
and GKE clusters.The text was updated successfully, but these errors were encountered: