Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync Devfile Registry and Helm Chart Ingress Handling #1539

Open
1 task
Jdubrick opened this issue May 7, 2024 · 0 comments
Open
1 task

Sync Devfile Registry and Helm Chart Ingress Handling #1539

Jdubrick opened this issue May 7, 2024 · 0 comments
Labels
area/registry Devfile registry for stacks and infrastructure

Comments

@Jdubrick
Copy link
Contributor

Jdubrick commented May 7, 2024

Which area/kind this issue is related to?

/area registry

Issue Description

After completion of #1520 we need to sync the way the Operator and the Helm chart deployments handle a missing Ingress domain. With the new changes to the Operator if an Ingress domain is not entered the creation of that resource is skipped and a log is output to communicate why it was skipped. Additionally, the fqdn is then set to http://localhost:8080 as a default as without an Ingress it won't be communicating outside of the cluster.

Changes made to the operator can be found here: devfile/registry-operator#89

Acceptance Criteria

  • Registry Operator & Helm Chart synced
@openshift-ci openshift-ci bot added the area/registry Devfile registry for stacks and infrastructure label May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/registry Devfile registry for stacks and infrastructure
Projects
Status: No status
Development

No branches or pull requests

1 participant