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

Ingress for Jenkins instance #896

Open
diptripa opened this issue Aug 24, 2023 · 9 comments
Open

Ingress for Jenkins instance #896

diptripa opened this issue Aug 24, 2023 · 9 comments
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers not-stale

Comments

@diptripa
Copy link

Describe the solution you'd like
Option Ingress resource for jenkins instance created using the operator

Describe alternatives you've considered
Creating ingress manually

@diptripa diptripa added the enhancement New feature or request label Aug 24, 2023
@brokenpip3 brokenpip3 added the good first issue Good for newcomers label Sep 4, 2023
@brokenpip3
Copy link
Collaborator

Yep this is a fair request, I marked it as "Good first issue", PRs are welcome :)

@github-actions github-actions bot added the stale label Nov 4, 2023
@AniketNS
Copy link

Hey @brokenpip3, I'd like to work on this issue. Will you please assign this to me?

@brokenpip3
Copy link
Collaborator

Done :)

@AniketNS
Copy link

May I trouble you, @brokenpip3, if I need any help?

@brokenpip3
Copy link
Collaborator

show me the code and I will help for sure, create a draft PR :)

@github-actions github-actions bot removed the stale label Nov 11, 2023
@AniketNS
Copy link

AniketNS commented Nov 12, 2023

Hello @brokenpip3, Will you please elaborate on the issue? and what should I supposed to do.

@brokenpip3
Copy link
Collaborator

Adding an ingress resource and the ingress values in the operator helm chart

@AniketNS
Copy link

AniketNS commented Jan 2, 2024

Hey @brokenpip3, I've opened the PR related to this issue. But the problem is I was also solving issue #937 and I've already opened the PR for that yesterday. But still when I'm trying to push the current code for the current issue with a new branch(a different branch that was used for the #937 issue) still that file is being added to PR.

Will you please guide me on how can I solve this problem?

@brokenpip3
Copy link
Collaborator

But still when I'm trying to push the current code for the current issue with a new branch(a different branch that was used for the #937 issue) still that file is being added to PR.

Will you please guide me on how can I solve this problem?

this is a git flow issue (or better it's the normal flow), you started the ingress branch from the history of the ldap branch, instead you need to start from the lastest master commit.
So you are in the AniketNS:ingress-jenkins branch right?
do the following

go here: https://github.com/AniketNS/kubernetes-operator/tree/master and force the sync

git reset HEAD~2
git stash
git fetch origin
git checkout master
git branch -D ingress-jenkins
git rebase <or merge> origin/master
git checkout -b ingress-jenkins
git stash pop
git commit -m "something" chart
git push origin ingress-jenkins --force-with-lease

but also you need to add more in the PR, the ingress needs to be optional, not enabled by default and you need to add the options in values.yaml

@github-actions github-actions bot added the stale label Apr 5, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 16, 2024
@brokenpip3 brokenpip3 reopened this Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers not-stale
Projects
None yet
3 participants