Fixup some missing/broken k8s configs

Summary: Discovered some small issues when recreating the testing cluster.

Test Plan: Deployed cloud to testing

Reviewers: michelle

Reviewed By: michelle
Signed-off-by: Vihang Mehta <vihang@pixielabs.ai>

Differential Revision: https://phab.corp.pixielabs.ai/D11702

GitOrigin-RevId: f54857a9f2d355f7e62a7baf4b3926877478d4d7

k8s/cloud/prod/kustomization.yaml

@@ -21,6 +21,7 @@ replicas:
   count: 3
 resources:
 - frontend_config.yaml
+- cloud_ingress_managed_cert.yaml
 - cloud_proxy_backend_config.yaml
 - vzconn_backend_config.yaml
 - ../base

k8s/cloud/staging/kustomization.yaml

@@ -19,6 +19,7 @@ replicas:
   count: 3
 resources:
 - frontend_config.yaml
+- cloud_ingress_managed_cert.yaml
 - cloud_proxy_backend_config.yaml
 - vzconn_backend_config.yaml
 - ../base

k8s/cloud/testing/cloud_proxy_backend_config.yaml

@@ -5,7 +5,7 @@ metadata:
   name: cloud-proxy-backend-config
 spec:
   securityPolicy:
-    name: pixie-cloud-staging-ingress-policy
+    name: pixie-cloud-testing-ingress-policy
   timeoutSec: 3600
   connectionDraining:
     drainingTimeoutSec: 60

k8s/cloud/testing/kustomization.yaml

@@ -19,6 +19,7 @@ replicas:
   count: 3
 resources:
 - frontend_config.yaml
+- cloud_ingress_managed_cert.yaml
 - cloud_proxy_backend_config.yaml
 - vzconn_backend_config.yaml
 - ../base

k8s/cloud/testing/vzconn_backend_config.yaml

@@ -5,7 +5,7 @@ metadata:
   name: vzconn-backend-config
 spec:
   securityPolicy:
-    name: pixie-cloud-staging-ingress-policy
+    name: pixie-cloud-testing-ingress-policy
   # This means that our streams will timeout after 1hr.
   timeoutSec: 3600
   cdn: