-
Notifications
You must be signed in to change notification settings - Fork 907
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
The key port and its value of connection secret didn't set to db-conn #1575
The key port and its value of connection secret didn't set to db-conn #1575
Comments
I'm not sure whether it was caused by crossplane or provider-alibaba, reading those specs and going through source code:) BTW, by hardcoding the value of
|
@zzxwill thanks for opening this! I think I know what is happening here and will have a fix in shortly :) The issue is likely that the |
This API spec does seem to indicate the the port should be present in the response from a |
However, it does not appear that |
@zzxwill after crossplane-contrib/provider-alibaba#19 I am seeing the port value appearing consistently :) Feel free to try it out again from apiVersion: packages.crossplane.io/v1alpha1
kind: ClusterPackageInstall
metadata:
name: provider-alibaba
namespace: crossplane-system
spec:
package: "crossplane/provider-alibaba:master" |
Cool, It worked. Thanks for the quick fix.
|
What happened?
For alibaba provider PoC, followed publish infrastructure to consume infrastructure by creating a pod with command
kubectl apply -f https://raw.githubusercontent.com/crossplane/crossplane/release-0.11/docs/snippets/publish/pod.yaml
and it failed.How can we reproduce it?
Follow instructions per publish infrastructure
What environment did it happen in?
Crossplane version:
Cloud provider or hardware configuration
Kubernetes version (use
kubectl version
)System Version: macOS 10.15.3 (19D76)
uname -a
)The text was updated successfully, but these errors were encountered: