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.

Sign up for GitHub

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

Jump to bottom

Update ibm_container_alb_cert to match new ingress controller requirement #2097

Closed
pauljegouic opened this issue Dec 8, 2020 · 6 comments
Closed

Update ibm_container_alb_cert to match new ingress controller requirement #2097

pauljegouic opened this issue Dec 8, 2020 · 6 comments
Assignees
@kavya498
Labels
service/Kubernetes Service Issues related to Kubernetes Service Issues

Comments

@pauljegouic
Copy link

Hello there,

Since 1st december, IKS provision an standard kubernetes ingress controller.

Therefore, some changes needs to be done, especially, the location of certificates.

  • Before 1st december: ingress controller was able to access ibm-cert-store namespace.
  • After 1st december: ingress controller can only access the namespace where you provision the ingress.

image

Source: https://cloud.ibm.com/docs/containers?topic=containers-ingress-types

Having said that, we need to have a namespace property as an input, to manage the target of the certificate copies in the cluster.
@pauljegouic
Copy link
Author

@hkantare

@hkantare
Copy link
Collaborator

hkantare commented Dec 8, 2020

We are analysing the issue

@kavya498 kavya498 self-assigned this Dec 17, 2020
kavya498 added a commit to kavya498/terraform-provider-ibm that referenced this issue Dec 18, 2020
@kavya498
Update IBM-Cloud#2097: Migrate to V2 and namespace support for ALB In…
00ae995 
…gress Secret
kavya498 added a commit to kavya498/terraform-provider-ibm that referenced this issue Dec 18, 2020
@kavya498
IBM-Cloud#2097 Vendor Changes
ba68047
hkantare pushed a commit that referenced this issue Dec 21, 2020
@kavya498 @hkantare
Update #2097: Migrate to V2 and namespace support for ALB Ingress Secret
22ba97c
hkantare pushed a commit that referenced this issue Dec 21, 2020
@kavya498 @hkantare
#2097 Vendor Changes
fa0a929
@kavya498
Copy link
Collaborator

Available in latest 1.18.0

@kavya498
Copy link
Collaborator

Can we close this issue?

@Nashluffy
Copy link
Contributor

As a part of this, shouldn't the terraform import command be updated to allow namespace specification?

For example,

terraform import certificate.ibm_container_alb_cert.cert <cluster-id>/<namespace>/<secret-name>

@kavya498 kavya498 added the service/Kubernetes Service Issues related to Kubernetes Service Issues label Mar 30, 2021
@hkantare
Copy link
Collaborator

we are closing the issue since the feature is a vaialble long back and docs updated accordingly
https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_alb_cert#import

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kavya498 kavya498

Labels
service/Kubernetes Service Issues related to Kubernetes Service Issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Nashluffy @hkantare @kavya498 @pauljegouic