Uploaded image for project: 'ONAP Operations Manager'
  1. ONAP Operations Manager
  2. OOM-1090

Portal VNC Pod failing to deploy on K8S v1.8+

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Medium Medium
    • None
    • Amsterdam Release
    • None

      As per this page (https://kubernetes.io/docs/concepts/workloads/pods/init-containers/), the "pod.beta.kubernetes.io/init-containers" annotation has been deprecated and unable to be used in kubernetes versions 1.8+, and now it needs to be defined in an init-containers in the spec section of the YAML, such as the one needed to deploy the portal VNC console (https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/portal/templates/portal-vnc-dep.yaml;h=d81a64e2c43723c5b4979da48f1df4323c5c643a;hb=refs/heads/amsterdam#l26).

       

      A quick grep shows that this annotation is being used not only in Portal, but in other ONAP components:

      https://gerrit.onap.org/r/gitweb?p=oom.git&a=search&h=refs%2Fheads%2Famsterdam&st=grep&s=pod.beta.kubernetes.io%2Finit-containers

       

      I made the changes in my local portal deployment and I was able to confirm that resolves the issue. The original issue is referenced here:

      https://lists.onap.org/pipermail/onap-discuss/2018-May/009592.html

       

            melliott melliott
            ha076r ha076r
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: