We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
apiVersion: jwt.vault.upbound.io/v1alpha1 kind: AuthBackend metadata: labels: crossplane.io/claim-name: "" crossplane.io/claim-namespace: "" name: jwt-xxx spec: deletionPolicy: Delete forProvider: boundIssuer: https://container.googleapis.com/v1/projects/xxx/locations/asia-southeast1-a/clusters/xxx oidcDiscoveryUrl: https://container.googleapis.com/v1/projects/xxx/locations/asia-southeast1-a/clusters/xxx path: xxx initProvider: {} managementPolicies: - '*' providerConfigRef: name: default
On version 2.0.1
It would error with
status: atProvider: {} conditions: - lastTransitionTime: "2025-01-13T08:51:58Z" reason: Creating status: "False" type: Ready - lastTransitionTime: "2025-01-13T10:01:37Z" message: "observe failed: failed to observe the resource: [{0 Error making API request.\n\nURL: GET https://xxx/v1/sys/mounts/auth/xxx\nCode: 405. Errors:\n\n* 1 error occurred:\n\t* unsupported operation\n\n []}]" reason: ReconcileError status: "False" type: Synced - lastTransitionTime: "2025-01-13T08:52:00Z" message: |- async create failed: failed to create the resource: [{0 error updating configuration to Vault for path jwt-xxx: Error making API request. URL: PUT https://xxx/v1/auth/xxx/config Code: 400. Errors: * error checking oidc discovery URL: 404 Not Found: { "error": { "code": 404, "message": "Requested entity was not found.", "status": "NOT_FOUND" } } []}] reason: AsyncCreateFailure status: "False" type: LastAsyncOperation
I switched back to 1.0.0, and the same spec could be created without a problem
The text was updated successfully, but these errors were encountered:
No branches or pull requests
On version 2.0.1
It would error with
I switched back to 1.0.0, and the same spec could be created without a problem
The text was updated successfully, but these errors were encountered: