pixie-io
Failed Deploy Pixie using YAML
Describe the bug I used self-hosted pixie. when i get to the third step “Deploy Pixie”
i deploy Pixie using YAML
when i Excuting an order
kubectl apply -f pixie_yamls/
the job 5ff7d47213a8875e3f1827d728b149498a0fdef08ba74499866d7d51a4b0147 in px-operator is not ready
The reason I found this error was ImagePullBackOff。
how can i modify this job yaml??
I tried to modify the job batch but got an error
I just want to modify imagePullPolicy or image. how can i modify this job yaml??
Hi @yang-maple , if I understand correctly, you want to use a version of the vizier-operator image from your own image registry. We use OLM to deploy/manage the vizier-operator, so you would have to push a new OLM bundle. That process is documented here: https://docs.px.dev/reference/admin/deploy-options/#custom-image-registry-collect-the-olm-images
Let us know if that works for you!
Hi @aimichelle . I tried using the link method you gave。but I can not push a new OLM bundle.
opm index export --index gcr.io/pixie-oss/pixie-prod/operator/bundle_index:0.0.1 is invalid。
then what should I do?
Hi @yang-maple , do you have access to pull from external registries from your host machine? (This does not to be run inside one of your K8s nodes).
No I can not. My cluster is an offline environment. So i can not access to pull from external registries.
Hi @yang-maple , do you have access to pull from external registries from your host machine? (This does not to be run inside one of your K8s nodes).
I also encountered this problem 。imagePullPolicy not modified 。
Follow the CRD description. If the image tag is not latest, then the imagePullPolicy is IfNotPresent, but the result is not like this
I also encountered this problem 。imagePullPolicy not modified 。
Follow the CRD description. If the image tag is not latest, then the imagePullPolicy is IfNotPresent, but the result is not like this