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.

Sign up for GitHub

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

Jump to bottom

Cluster API fetchConfig accepting self-hosted gitlab installations #705

Open
ts-mini opened this issue Jan 30, 2025 · 1 comment · May be fixed by #706
Open

Cluster API fetchConfig accepting self-hosted gitlab installations #705

ts-mini opened this issue Jan 30, 2025 · 1 comment · May be fixed by #706
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@ts-mini
Copy link
Contributor

ts-mini commented Jan 30, 2025 •
edited
Loading

User Story

As a operator I would like to deployed a cluster-api-providers from self-managed gitlab installations that dont match gitlab. without using the 'airgapped' deployment mechanism

Detailed Description

Currently, the code only accepts gitlab installations that start with gitlab. and github installations that end in github.com. The goal would be to allow fetchConfig the ability to accept a url that doesn't match this explicit pattern as both tools offer self hosting capabilities.

This is different than #488 as its attempting to use fetchConfig where we have network, just against custom gitlab domains
/kind feature
@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 30, 2025
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If CAPI Operator contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@ts-mini ts-mini linked a pull request Jan 30, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

✨ gitlab fetchConfig regexp ts-mini/cluster-api-operator
2 participants
@ts-mini @k8s-ci-robot