Porter Operator CrashLoopBackOff

[hemantkathuria]

I have created a new installation against the CNAB published in my ACR.

I am trying to use porter operator on AKS. I have gone ahead and have created a AgentConfig by copy the default one and added the storage class for azure in it.

I have also added the imagepullseceret for porter-agent service account.

Now suddenly my porter operator is going in failed state.

porter-operator-system porter-operator-controller-manager-744d4cc48f-w2q5d 1/2 CrashLoopBackOff 10 (2m37s ago) 38m

kubectl logs porter-operator-controller-manager-744d4cc48f-w2q5d -n porter-operator-system Defaulted container "kube-rbac-proxy" out of: kube-rbac-proxy, manager I1029 05:11:04.178826 1 main.go:186] Valid token audiences: I1029 05:11:04.179047 1 main.go:232] Generating self signed cert as no cert is provided I1029 05:11:04.406147 1 main.go:281] Starting TCP socket on 0.0.0.0:8443 I1029 05:11:04.406688 1 main.go:288] Listening securely on 0.0.0.0:8443

I am not getting much information to determine why it is going in crashloopbackoff state. Please help

Also, is there is a way to get a callback when the installation completes? I need to know if it is completed or not and if failed what was the issue. In regular porter install it waits until it completes.

Name: azuredep-85 Namespace: unifieddeployment Labels: Annotations: API Version: getporter.org/v1 Kind: Installation Metadata: Creation Timestamp: 2023-10-29T05:44:17Z Generation: 1 Resource Version: 459742 UID: 6986ecf9-58c1-4c3f-8680-69131ca82521 Spec: Agent Config: Name: customagentconfig Bundle: Repository: crporterpoc.azurecr.io/porter-hello Version: v0.1.0 Credential Sets: azurecredsetnew Name: azuredep-85 Namespace: unifieddeployment Parameters: Location: EastUs2 storage_account_name: porterdemo85 storage_container_name: container001 storage_rg: porterdemo85 Schema Version: 1.0.2 Events: