Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "defaulting.webhook.provisioners.karpenter.sh": Post "https://karpenter.karpenter-fargate.svc:443/default-resource?timeout=10s": x509: certificate is valid for karpenter-webhook, karpenter-webhook.karpenter-fargate, karpenter-webhook.karpenter-fargate.svc, karpenter-webhook.karpenter-fargate.svc.cluster.local, not karpenter.karpenter-fargate.svc

[sandynew]

Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "defaulting.webhook.provisioners.karpenter.sh": Post "https://karpenter.karpenter-fargate.svc:443/default-resource?timeout=10s": x509: certificate is valid for karpenter-webhook, karpenter-webhook.karpenter-fargate, karpenter-webhook.karpenter-fargate.svc, karpenter-webhook.karpenter-fargate.svc.cluster.local, not karpenter.karpenter-fargate.svc.

I am facing above issue while deploying the provisioners in to eks fargate.

Please find the code details:

cat <<EOF | kubectl apply -f -
apiVersion: karpenter.sh/v1alpha5
kind: Provisioner
metadata:
name: default
spec:
requirements:
- key: karpenter.sh/capacity-type
operator: In
values: ["spot"]
limits:
resources:
cpu: 1000
provider:
subnetSelector:
karpenter.sh/discovery: ${CLUSTER_NAME}
securityGroupSelector:
karpenter.sh/discovery: ${CLUSTER_NAME}
ttlSecondsAfterEmpty: 30
EOF

I am following below mentioned article to configure the karpenter.
URL: https://karpenter.sh/v0.6.3/getting-started/

Environment details::

• Kubernetes version: 1.21
• Install method: static manifests

/kind bug

[jahrlin]

Hi,

It seems that your Certificate is not configured with the hostname karpenter.karpenter-fargate.svc - can you try adding this?

[jetstack-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle stale

[jetstack-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle rotten
/remove-lifecycle stale

[jetstack-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/close

[jetstack-bot]

@jetstack-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.