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

create AWSManagedControlPlane fails in a private vpc due to IAM API requirement #4894

Open
AhyeongLee opened this issue Mar 26, 2024 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@AhyeongLee
Copy link

/kind bug

What steps did you take and what happened:
[A clear and concise description of what the bug is.]

I applied below AWSManagedControlPlane

apiVersion: controlplane.cluster.x-k8s.io/v1beta2
kind: AWSManagedControlPlane
metadata:
  name: my-cluster-control-plane
  namespace: cluster-api
spec:
  region: ap-northeast-2
  version: v1.27.0
  network:
    vpc:
      id: vpc-id
    subnets:
    - id: subnet-id1
    - id: subnet-id2
  bastion:
    enabled: false
  roleName: TEST-ROLE

And I got error message

E0326 07:44:29.203901       1 controller.go:329] "Reconciler error" err=<
        failed to reconcile control plane for AWSManagedControlPlane cluster-api/aylee-cluster-control-plane: RequestError: send request failed
        caused by: Post "https://iam.amazonaws.com/": dial tcp 44.216.198.236:443: i/o timeout

My VPC is private and there's no VPC Endpoint available for IAM api
I am curious about how to create an AWSManagedControlPlane in a private vpc.

What did you expect to happen:

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • Cluster-api-provider-aws version: cluster-api-aws-controller:v2.4.1
  • Kubernetes version: (use kubectl version): 1.27
  • OS (e.g. from /etc/os-release):
@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. needs-priority labels Mar 26, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If CAPA/CAPI 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/test-infra repository.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Mar 26, 2024
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. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants