-
Notifications
You must be signed in to change notification settings - Fork 33
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
Operator gets stuck at Waiting for service to be created
#45
Comments
It seems to work when using the |
Waiting for service to be created Can you describe the service and check why is not getting ready? kubectl describe service VPN_NAME-svc |
The service is ready, I've switched to a ClusterIP service for debugging purposes.
P.S: I've noticed these AWS load-balancer annotations, why do these exist, I'm on a self-hosted k8s |
They are currently hard-coded in the controller, soon you will be able to specify your own annotations: |
I'm going to close this, as the main branch works and only a new release is required. |
Describe the bug
When creating a new WireGuard resource, the operator creates services and secrets, but doesn't create the deployment, the status is stuck at
Waiting for service to be created
.To Reproduce
Steps to reproduce the behavior:
Wireguard
andWireguardPeer
Wireguard
resource as YAML and seestatus.message
fieldExpected behavior
It should create the deployment.
Additional context
K8s version: 1.27.1
OS: Talos Linux v1.4.1
wireguard-operator version: 1.0.1
The text was updated successfully, but these errors were encountered: