Uploaded image for project: 'Openshift sandboxed containers'
  1. Openshift sandboxed containers
  2. KATA-3426

InitData support for peer pods

XMLWordPrintable

    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • Hide
      .initdata for {cc}

      {cc} now support the `initdata` specification for configuring a peer pod at runtime, avoiding the need to embed sensitive data in the peer pod virtual machine image. This feature enhances security by reducing exposure of confidential information and improves flexibility by eliminating custom image builds. You can apply an `initdata` configuration globally or to a specific pod.
      Show
      .initdata for {cc} {cc} now support the `initdata` specification for configuring a peer pod at runtime, avoiding the need to embed sensitive data in the peer pod virtual machine image. This feature enhances security by reducing exposure of confidential information and improves flexibility by eliminating custom image builds. You can apply an `initdata` configuration globally or to a specific pod.
    • Feature
    • Done
    • 0

       (mandatory if we use CoCo 0.10.0)

      Ability to provide bootstrap configuration like KBS address, certificates, agent policies etc as pod annotation.

      Ref: https://github.com/confidential-containers/cloud-api-adaptor/blob/main/src/cloud-api-adaptor/docs/initdata.md 

       

      • Investigate upgrade requirements from a 1.7.0 created pod vm image to 1.8.0 pod vm image w.r.to initData requirements. Can the old image work with 1.8.0 code ?
      • Add documentationHCIDOCS-532
      • Tests
      •  

              astillma Andy Stillman
              jrope Julien ROPE
              John Wilkins John Wilkins
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: