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

domain.opensearchservice: vpc endpoint URI does not appear in status.atProvider #1994

Closed
kkendzia opened this issue Feb 6, 2024 · 1 comment
Labels
bug Something isn't working stale

Comments

@kkendzia
Copy link

kkendzia commented Feb 6, 2024

What happened?

When creating a Domain or a Server it also creates, with the correct configuration, a VPC Endpoint. Unfortunately the only possiblity to retrieve the URI is by using aws-cli (or console), because the information won't be added to the status output of the resources.

DomainStatus.Endpoints.vpc provides you with the necessary URI, but https://github.com/crossplane-contrib/provider-aws/blob/master/pkg/controller/opensearchservice/domain/zz_controller.go#L353 somehow doesn't map it correctly apparently.

This is the response of the aws-cli call.

bash-4.2# aws opensearch describe-domain --domain-name <domainname>
{
    "DomainStatus": {
        "DomainId": "<domainid>",
        "DomainName": "<domainname",
        "ARN": "<domainArn>",
        "Created": true,
        "Deleted": false,
        "Endpoints": {
            "vpc": "vpc-<domainname>-<hash>.eu-central-1.es.amazonaws.com"
        },
....

How can we reproduce it?

Create a Domain and take a look at status of the resource

What environment did it happen in?

Crossplane version: 1.14.5

kubectl version
Client Version: v1.28.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.24.17-eks-5e0fdde

@kkendzia kkendzia added the bug Something isn't working label Feb 6, 2024
Copy link

github-actions bot commented May 7, 2024

Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

@github-actions github-actions bot added the stale label May 7, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale
Projects
None yet
Development

No branches or pull requests

1 participant