Skip to content
This repository has been archived by the owner on Aug 19, 2024. It is now read-only.

Support k8s ingress #346

Closed
tomassatka opened this issue Apr 25, 2024 · 2 comments
Closed

Support k8s ingress #346

tomassatka opened this issue Apr 25, 2024 · 2 comments
Labels
jira Issue will be sync'ed to Red Hat JIRA

Comments

@tomassatka
Copy link

hi Team

We use your backstage operator. Really cool. But we install it into aks instead of openshift so added ingress pkg that it is deployed instead of route. I did this modification on code of 1.1.x tag. I can see that main has changed a lot, so reconciliation of each deployable resource is now in pkg directory and uses interface.

  • Do you consider to create ingress to support plain k8s?
  • I am happy to contribute but do i have to checkout main and contribute against main or can i provide the updated 1.1.x?

thx

@github-actions github-actions bot added the jira Issue will be sync'ed to Red Hat JIRA label Apr 25, 2024
@gazarenkov
Copy link
Member

Hi @tomassatka

Good thing!
Go ahead with main branch (1.1.x is for bug fixes only).

@nickboldt
Copy link
Member

As part of the migration from janus-idp to redhat-developer in https://issues.redhat.com/browse/RHIDP-1021, this will be tracked in https://issues.redhat.com/browse/RHIDP-2176

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
jira Issue will be sync'ed to Red Hat JIRA
Projects
None yet
Development

No branches or pull requests

3 participants