I am attempting to install the Azure Policy extension on a newly deployed Arc Kubernetes cluster.
az k8s-extension delete --cluster-type connectedClusters --cluster-name azure-arc-test-01 --resource-group arc-enabled-kubernetes-poc --name azurepolicy
However, I am getting the following error:
Code: ExtensionOperationFailed
Message: The extension operation failed with the following error:
Error: {failed to install chart from path [] for release [azurepolicy]:
err [unable to build kubernetes objects from release manifest:
unable to recognize "": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1"]} occurred while doing the operation :
{Installing the extension} on the config.
Kubernetes version is 1.25.
I believe that the error might be caused by the fact that PodSecurityPolicy is located in extensions/v1beta1 and not in policy/v1beta - discussed here: https://github.com/helm/charts/issues/8789#issuecomment-433811260
I am looking for suggestions on how I could get around this issue. Specifically, could I download the required Helm chart and point to extensions/v1beta1?
Related
Rancher version: v2.6.8
AWS EKS cluster version: 1.2.1
I created another Rancher and I accidentally executed the yaml provided by this Rancher on cluster A. I delete cluster A in Rancher and try to reimport it. Now it's not working properly.
[Error] Error while applying agent YAML, it will be retried automatically: exit status 1, Error from server (InternalError): an error on the server ("unable to create impersonator account: error setting up impersonation for user u-qjbo6ceucp: impersonation: error creating secret for service account cattle-impersonation-u-qjbo6ceucp") has prevented the request from succeeding
I deleted the cluster in Rancher, tried importing in new Rancher, got the same error.
We want to install multiple istio control plane on same kubernetes cluster.
We installed istio by like
istioctl install -f istioOperator.yaml
istioOperator.yaml is based on
istioctl profile dump minimal
And it is further modified by changing istioNamespace, metadata/namespace and restricting namespaces in the mesh by discoverySelector.
When installing second istio in the same way, an error occurred like below (istio-system-la is second istio's namespace).
✔ Istio core installed
- Processing resources for Istiod.
2022-07-13T05:32:17.577423Z error installer failed to update resource with server-side apply for obj EnvoyFilter/istio-system-la/stats-filter-1.11: Internal error occurred: failed calling webhook "rev.validation.istio.io": failed to call webhook: Post "https://istiod.istio-system-la.svc:443/validate?timeout=10s": service "istiod" not found
...
How can we avoid this error, and successfully for istios to coexisting?
I am trying to install JanusGraph on google cloud using the tutorial available at the https://cloud.google.com/architecture/running-janusgraph-with-bigtable
But i am getting an error unable to recognize "": no matches for kind "Deployment" in version "apps/v1beta1", and getting the chart deprecated error . Let me know if any one is able to install the same,
With as per the documentation
gcloud container clusters create janusgraph-tutorial \
--cluster-version=1.15 \
--machine-type=n1-standard-4 \
--scopes=\
"https://www.googleapis.com/auth/bigtable.admin",\
"https://www.googleapis.com/auth/bigtable.data"
The error was ERROR: (gcloud.container.clusters.create) ResponseError: code=400, message=No valid versions with the prefix "1.15" found.
So i tried:
gcloud container ...
--cluster-version=1.20 \ ..
and i was able to create the container
later janus graph installation
helm upgrade --install --wait --timeout 600s janusgraph stable/janusgraph -f values.yaml
Release "janusgraph" does not exist. Installing it now.
WARNING: This chart is deprecated
Error: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "Deployment" in version "apps/v1beta1", unable to recognize "": no matches for kind "StatefulSet" in version "apps/v1beta1"]
Kubernetes versions resources like Deployment. Until recently (<=1.16), Deployment was available under the apps/v1beta1 API (version). Since Kubernetes 1.16 this is deprecated and removed. You must now use apps/v1.
See:
Deprecated APIs Removed in 1.16
Kubernetes API Reference 1.21
If you're able to revise these references in the tutorial, then you should do so. You may encounter other APIs that are deprecated and|or removed but only the latter should cause similar problems.
It may be preferable to "Send feedback" (bottom of tutorial) to Google asking that someone there upgrade the tutorial or provide caveats.
Curiously, I noticed that the tutorial includes creating a Kubernetes v1.15 cluster:
gcloud container clusters create janusgraph-tutorial \
--cluster-version=1.15 \
...
Per the above, that version should still support apps/v1beta1/Deployment did that not work?
Your question would benefit from additional context|detail. You write "I am getting an error" but you do not include the specific step that cause this issue. I assume it was when you attempted to deploy JanusGraph to the cluster using Helm?
helm upgrade --install ... 600s janusgraph stable/janusgraph -f values.yaml
When I try to create a Jenkins X Kubernetes cluster with GKE using this command:
jx create cluster gke --skip-login
The following exeption is thrown at the end of installation:
error creating cluster configuring Jenkins: creating Jenkins API token: after 3 attempts, last error: creating Jenkins Auth configuration: secrets "jenkins" not found
During installation I select the default settings and provide my own github settings, including generated personal access token, but I don't think that the github token is the issue in this case (I'm pretty sure all my github settings are correct)
The problem has been solved by using --tekton flag:
jx create cluster gke --skip-login --tekton
I downloaded the kube-batch in my local PC. Now, when I try to deploy the kube-batch using helm, I got the following error:
Error: customresourcedefinitions.apiextensions.k8s.io "podgroups.scheduling.incubator.k8s.io" already exists
It appears after using the helm
How can I fix this error?
Adjust apiVersion in /src/github.com/hamikube/kube-batch/deployment/kube-batch/Chart.yaml to a version Helm accepts (v1 instead of v1alpha1 in this case).
Thought the API should then comply to v1 in order to avoid other errors.