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

Provide helm option to specify API server address #12398

Open
ttc0419 opened this issue Nov 21, 2024 · 4 comments
Open

Provide helm option to specify API server address #12398

ttc0419 opened this issue Nov 21, 2024 · 4 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@ttc0419
Copy link

ttc0419 commented Nov 21, 2024

Please provide an helm option to specify the API server address. The webhook job and controller uses the service IP to talk to the API server. But some setup might not have service ready (e.g. kube-proxy not installed or using passthrough CNIs like MAC/IP VLAN). Which causes it fail to install.

@ttc0419 ttc0419 added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 21, 2024
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Nov 21, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If Ingress 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.

@longwuyuan
Copy link
Contributor

Your issue description is too short. It does not help all readers get the summary of the problem as in a real use case of doing an install of the controller or a ingress.

@ttc0419
Copy link
Author

ttc0419 commented Nov 22, 2024

Your issue description is too short. It does not help all readers get the summary of the problem as in a real use case of doing an install of the controller or a ingress.

Updated, the problem is it fails to install when the kubernetes service is not available but it does not provide an alternative API server addresses.

@longwuyuan
Copy link
Contributor

I think we will have to wait till someone understands what you are saying and is able to make useful comments here, to help you.

The template of a new bug report asks questions. You can click the button for new bug report and see the questions there. Then you can edit this issue description, and answer those questions in markdown format. This way there will be some small details available for readers.

Can you copy/paste the exact and complete real command you typed, in full detail, without redacting, and also copy/paste the response error messages or logs etc, that you got after typing that command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Development

No branches or pull requests

3 participants