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

[Bug]: No endpoints available for service "upbound-provider-aws-s3" #1656

Closed
1 task done
reiinoldo opened this issue Jan 31, 2025 · 1 comment
Closed
1 task done
Labels
bug Something isn't working needs:triage

Comments

@reiinoldo
Copy link

reiinoldo commented Jan 31, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Affected Resource(s)

  • s3.aws.upbound.io/v1beta1

Resource MRs required to reproduce the bug

apiVersion: s3.aws.upbound.io/v1beta1
kind: Bucket
metadata:
  name: mybucket
  namespace: dev-reporting
spec:
  forProvider:
    region: us-east-1

Steps to Reproduce

kubectl apply -f .\base\s3-bucket.yaml
output: bucket.s3.aws.upbound.io/mybucket created
kubectl describe Bucket
output: Error from server: conversion webhook for s3.aws.upbound.io/v1beta1, Kind=Bucket failed: Post "https://upbound-provider-aws-s3.crossplane-system.svc:9443/convert?timeout=30s": no endpoints available for service "upbound-provider-aws-s3"

What happened?

When trying to create a S3 Bucket seems that there an outstage from the upbound-provider-aws-s3 endpoints

Relevant Error Output Snippet

 Error from server: conversion webhook for s3.aws.upbound.io/v1beta1, Kind=Bucket failed: Post "https://upbound-provider-aws-s3.crossplane-system.svc:9443/convert?timeout=30s": no endpoints available for service "upbound-provider-aws-s3"

Crossplane Version

v1.17.2

Provider Version

v1.17.0

Kubernetes Version

v1.31.1

Kubernetes Distribution

No response

Additional Info

No response

@reiinoldo reiinoldo added bug Something isn't working needs:triage labels Jan 31, 2025
@reiinoldo
Copy link
Author

My bad, the provider pod was down due a limitation of pods. I've fixed.
The issue can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs:triage
Projects
None yet
Development

No branches or pull requests

1 participant