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

Serverless webhook always crashes initially #78

Closed
kwiatekus opened this issue Mar 21, 2023 · 5 comments
Closed

Serverless webhook always crashes initially #78

kwiatekus opened this issue Mar 21, 2023 · 5 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. wontfix This will not be worked on

Comments

@kwiatekus
Copy link
Contributor

kwiatekus commented Mar 21, 2023

Description

Investigate why serverless webhook always crashes initially. After restart it works.
Also - it starts considerably long

Steps to reproduce

Deploy kyma cluster essentials:

kyma provision k3d
kyma deploy -s main --component cluster-essentials

Install serverless-manager

kubectl apply - f https://github.com/kyma-project/serverless-manager/releases/latest/download/serverless-manager.yaml

Apply sample serverless CR

kubectl apply - f https://raw.githubusercontent.com/kyma-project/serverless-manager/main/config/samples/operator_v1alpha1_serverless_k3d.yaml

Observe restart of webhook:

kubectl get pods -n kyma-system -w                                                                                                                                                                   NAME                                                     READY   STATUS    RESTARTS   AGE
serverless-manager-controller-manager-7ff5c47c69-7wwsd   2/2     Running   0          28s
serverless-ctrl-mngr-57b9466f65-rhr8r                    0/1     Running   0          9s
serverless-webhook-svc-558bdb78c6-bk88k                  0/1     Running   0          9s
serverless-webhook-svc-558bdb78c6-bk88k                  0/1     Error     0          13s
serverless-webhook-svc-558bdb78c6-bk88k                  0/1     Running   1 (1s ago)   14s

Error log

{"level":"ERROR","timestamp":"2023-03-22T08:41:24Z","caller":"webhook/main.go:107","message":"failed to read caBundle file: /tmp/k8s-webhook-server/serving-certs/server-cert.pem: open /tmp/k8s-webhook-server/serving-certs/server-cert.pem: no such file or directoryfailed to setup certificates and webhook secret","context":{}}

Attachment
Alternatively follow steps described in the scenario
https://killercoda.com/kyma-project/scenario/serverless

Related
Depends on #7

@kwiatekus kwiatekus added the kind/bug Categorizes issue or PR as related to a bug. label Mar 21, 2023
@pbochynski
Copy link
Contributor

pbochynski commented Mar 22, 2023

Actually it fails now permanently (at least on killercoda)
The function CRD from main doesn't work with the current release after this change:
kyma-project/kyma#17090

@kyma-bot
Copy link
Contributor

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

@kyma-bot kyma-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 22, 2023
@kwiatekus kwiatekus removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 24, 2023
@kwiatekus
Copy link
Contributor Author

Blocked because we want check if we need webhook at all
kyma-project/kyma#17562

@kyma-bot
Copy link
Contributor

kyma-bot commented Aug 1, 2023

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

@kyma-bot kyma-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 1, 2023
@kwiatekus kwiatekus removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 1, 2023
@kwiatekus
Copy link
Contributor Author

Closing in favor of #247

@kwiatekus kwiatekus added the wontfix This will not be worked on label Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants