Uploaded image for project: 'Open Data Hub'
  1. Open Data Hub
  2. ODH-450

ODH Operator not respecting openshift cluster-proxy

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • operator
    • None

      Issue migrated from github

      Describe the bug
      After deploying the ODH Operator from the OperatorHub in OCP (4.6.8), deploying an Open Data Hub KfDef fails to pull the manifests and kf-manifests when behind an enterprise Proxy with a custom certificate authority. The proxy and trusted-CA are both defined in the global configuration cluster-proxy.

      To Reproduce
      Steps to reproduce the behavior:

      1. Install the ODH 0.9.0 Operator from OperatorHub to -n openshift-operators
      2. Create an ODH Namespace/Project
      3. Deploy a standard KfDef template without modifications to -n odh.
      4. The ODH Operator will have the following in the error logs unable to pull from GitHub.

      $ oc logs opendatahub-operator-7cf7cb66fb-5gmzn -n openshift-operators
      ...
      time="2021-01-28T16:59:02Z" level=info msg="Creating directory /tmp/odh/opendatahub/.cache"
      time="2021-01-28T16:59:02Z" level=info msg="Fetching https://github.com/opendatahub-io/manifests/tarball/master to /tmp/odh/opendatahub/.cache/kf-manifests"
      time="2021-01-28T17:01:14Z" level=error msg="failed to build kfApp from URI /tmp/odh/opendatahub/config.yaml: Error: couldn't generate KfApp: (kubeflow.error): Code 500 with message: could not sync cache. Error: (kubeflow.error): Code 400 with message: couldn't download URI https://github.com/opendatahub-io/manifests/tarball/master: Get https://github.com/opendatahub-io/manifests/tarball/master: dial tcp 140.82.112.4:443: connect: connection timed out."
      time="2021-01-28T17:01:14Z" level=error msg="Failed to load KfApp. Error: couldn't generate KfApp: (kubeflow.error): Code 500 with message: could not sync cache. Error: (kubeflow.error): Code 400 with message: couldn't download URI https://github.com/opendatahub-io/manifests/tarball/master: Get https://github.com/opendatahub-io/manifests/tarball/master: dial tcp 140.82.112.4:443: connect: connection timed out."

      Expected behavior
      Expected that the ODH Operator will use cluster-proxy settings to reach the Internet through Proxy / custom-CA.

      Additional context
      Current work around is to download the manifests and rehost temporarily on a non-HTTPS system internally.

              llasmith@redhat.com Landon LaSmith
              rhn-support-jnakfour Juana Nakfour (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: