first-operator install failed on OCP 4.7.45

[dove-young]

What happened:

[root@st2 ~]# kubectl kudo init -v 9
init cmd &{0xc00012e008 0xc00012e010 0x29722d8  Always false   kudo-system  false 300 false false false false /root/.kudo <nil> false}
/root/.kudo exists
/root/.kudo/repository exists
/root/.kudo/repository/repositories.yaml exists
$KUDO_HOME has been configured at /root/.kudo
create client
configuration from "/root/.kube/config" finds host https://api.st2.example.com:6443
Run pre-install verify
Try to retrieve cert-manager CRD certificates.cert-manager.io
Got CRD. Group: cert-manager.io, Version: v1
Detected cert-manager CRDs /
Detected cert-manager cert-manager.io/v1
CRD certificates.cert-manager.io is served with version v1
CRD issuers.cert-manager.io is served with version v1
Warnings
unable to find cert-manager deployment. Make sure cert-manager is running.
✅ installed crds
✅ installed namespace
✅ installed service account
Warning: admissionregistration.k8s.io/v1beta1 MutatingWebhookConfiguration is deprecated in v1.16+, unavailable in v1.22+; use admissionregistration.k8s.io/v1 MutatingWebhookConfiguration
✅ installed webhook
try to delete manager stateful set kudo-system/kudo-controller-manager before creating it
Uninstall KUDO manager stateful set
Deleting obj kudo-system/kudo-controller-manager is already NotFound, return now
try to delete manager service kudo-system/kudo-controller-manager-service before creating it
Uninstall KUDO manager service
Deleting obj kudo-system/kudo-controller-manager-service is already NotFound, return now
✅ installed kudo controller
[root@st2 ~]#
[root@st2 ~]#
[root@st2 ~]# kubectl kudo install ./first-operator -v 9
repo configs: { name:community, url:https://kudo-repository.storage.googleapis.com/v1 }

repository used { name:community, url:https://kudo-repository.storage.googleapis.com/v1 }
acquiring kudo client
getting operator package
determining package type of /root/first-operator
local operator discovered: /root/first-operator
folder walking through directory first-operator
folder walking through directory templates
Preparing default/first-operator:0.1.0 for installation
parameters in use: map[]
operator.kudo.dev default/first-operator does not exist

operator default/first-operator created
operatorversion default/first-operator-1.7.9-0.1.0 created
Error: failed to install instance default/first-operator-instance: installing Instance: Internal error occurred: failed calling webhook "instance-admission.kudo.dev": Post "https://kudo-controller-manager-service.kudo-system.svc:443/admit-kudo-dev-v1beta1-instance?timeout=30s": no endpoints available for service "kudo-controller-manager-service"
[root@st2 ~]#

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

• construct your first-operator as pipe-task sample in this url https://kudo.dev/docs/developing-operators/tasks.html#pipe-task
• install it to OCP 4.7.45

Anything else we need to know?:

• retry install first-operator it works

[root@st2 ~]# kubectl kudo install ./first-operator -v 9
repo configs: { name:community, url:https://kudo-repository.storage.googleapis.com/v1 }

repository used { name:community, url:https://kudo-repository.storage.googleapis.com/v1 }
acquiring kudo client
getting operator package
determining package type of /root/first-operator
local operator discovered: /root/first-operator
folder walking through directory first-operator
folder walking through directory templates
Preparing default/first-operator:0.1.0 for installation
parameters in use: map[]
operator.kudo.dev default/first-operator unchanged
operatorversion default/first-operator-1.7.9-0.1.0 already installed
instance first-operator-instance created in namespace default
instance default/first-operator-instance created
[root@st2 ~]#

Environment:

• Kubernetes version (use kubectl version):
• Kudo version (use kubectl kudo version):
• Operator:
• operatorVersion:
• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

you can find env details in this issue #1807