Create an api using tyk gateway k8s through tyk-operator

Hi Team,
I’m using Tyk gateway k8s deployment through tyk operator and Iam using this links.
1.GitHub - TykTechnologies/tyk-oss-k8s-deployment: Deployment yamls to run Tyk Gateway and Redis in a Kubernetes environment
2. GitHub - TykTechnologies/tyk-operator: Tyk Operator for Kubernetes
My tyk gateway k8s is deployment is working fine.
helm install foo -n tyk-operator-system /home/new/tyk_opes/tyk-operator/helm
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /home/azureuser/.kube/config
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /home/azureuser/.kube/config
NAME: foo
LAST DEPLOYED: Mon Aug 28 09:53:24 2023
NAMESPACE: tyk-operator-system
STATUS: deployed
You have deployed the tyk-operator! See GitHub - TykTechnologies/tyk-operator: Tyk Operator for Kubernetes for more information.
Thanks in advance.
$ kubectl apply -f httpbin.yaml
To create an api it shows this error.
Error from server (InternalError): error when creating “test/test.yaml”: Internal error occurred: failed calling webhook “”: Post https://foo-webhook-service.tyk-operator-system.svc:443/mutate-tyk-tyk-io-v1alpha1-apidefinition?timeout=30s: service “foo-webhook-service” not found issue.

Think this Github issue is related to your error and this suggestion solves it.

I think I found the issue, don’t override full name when helm installing

change this

helm install foo ./helm -n tyk-operator-system --set fullnameOverride=foo


helm install foo ./helm -n tyk-operator-system

I think this will fix the webhook service name and resolve the webhook calls.

Let us know how it turns out