Knative with Private Docker Regis

[TimothySutton81]

What version of Knative?

1.5.0

Expected Behavior

Deploying an image from local docker registry that is in kubernetes cluster along side deployed knative service controller using the knative operator fails with DNS resolution issue.

Actual Behavior

Knative service controller gets a dns error when fetching the image from local docker repository. This can be worked around by manually editing the controller deployed by operator that gets deploy by the operator, and changing the dns settings. One would think you could set this on deployment, either when enabling servicing or when the operator is deployed.

Steps to Reproduce the Problem

Deploy docker registry to your kubernetes cluster that goes by a domain name, in my case it was docker-registry (all host machines in cluster have host tables updated for this, and opendns/kubedns service resolve this name to ip address). Then deploy knative operator and then enable knative service (following these instructions https://knative.dev/docs/install/operator/knative-with-operators/). Then try to deploy a service from your local repository, and get failure. I was forced to update the dns setting and network.

I think there is some CRDs that would be nice to haves here with CRDs, I was also forced to edit the deployed controller for CA settings following these instructions https://github.com/projectriff/riff/issues/1098#issuecomment-487377467.

Issue can is further documented here.

https://groups.google.com/g/knative-users/c/uCnG_V3mJdE

[github-actions[bot]]

This issue is stale because it has been open for 90 days with no activity. It will automatically close after 30 more days of inactivity. Reopen the issue with /reopen. Mark the issue as fresh by adding the comment /remove-lifecycle stale.

[knative-prow-robot]

This issue or pull request is stale because it has been open for 90 days with no activity.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close

/lifecycle stale

[github-actions[bot]]

This issue is stale because it has been open for 90 days with no activity. It will automatically close after 30 more days of inactivity. Reopen the issue with /reopen. Mark the issue as fresh by adding the comment /remove-lifecycle stale.