Uploaded image for project: 'Service Binding'
  1. Service Binding
  2. APPSVC-1147

Remove the dependency on creating a secret containing kubeconfig when testing sbo helm chart

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Service Binding
    • None

      Owner: Architect:

      Kartikey

      Story (Required)

      As an SBO user I would like to be able to install SBO in K8 via helm charts and be able to run helm test without having to pass my kubeconfig as an environment or volume to the helm test pod.

      Background (Required)

      It is possible to talk to K8 API from inside a container, it is redundant to have use specify the kubeconfig again when running helm test.

      Glossary

      NA

      Out of scope

      NA

      In Scope

      NA

      Approach(Required)

      The console is run from within a POD and it can access the K8 API without additional kubeconfig info. Also take a look at https://kubernetes.io/docs/tasks/run-application/access-api-from-pod/

      Dependencies

      NA

      Edge Case

      NA

      Acceptance Criteria

      We should be able to test sbo helm chart without creating a secret from kubeconfig.

      INVEST Checklist

      Dependencies identified
      Blockers noted and expected delivery timelines set
      Design is implementable
      Acceptance criteria agreed upon
      Story estimated

      Legend

      Unknown
      Verified
      Unsatisfied

              Unassigned Unassigned
              kmamgain@redhat.com Kartikey Mamgain (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: