-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Whether there are bugs or security risks when using the following extensions(kubernetes.podspec-affinity,kubernetes.podspec-persistent-volume-claim,kubernetes.podspec-persistent-volume-write) of knative? #14918
Comments
Hi @zzuchen wrt pvcs here is a related comment about maturity: knative/docs#5736 (comment), we would like to move it to GA. |
Thank you for your answer, but I am not using the latest version of knaitve. Are there any improvements in supporting pvc in knaitve version 1.3 and 1.13? Is pvc also mature in knative 1.3 version, can it reach the beta stage or GA stage? |
The feature was been used for quite some time so its pretty stable. 1.3 is quite old, I would recommend to upgrade. |
Thank you for your reply. As we are currently unable to update to the latest version of knaitve, we can only use version 1.3 at most. Therefore, may I ask if there have been any reported errors using PVC functionality in this lower version of knaitve? |
Not any that I am aware of. You can try it and report back btw. |
Thank you very much,what‘s more, I have read your submit record about PVC(0682e94), did you only add the validation of the PVC volume in the process of validatevolume of the admission controller? |
Thank you very much,I don't have any more questions. |
Ask your question here:
I am using Krative 1.3 version, and due to the need to set pod anti affinity and PVC, I need to enable kubernetes.podspec-affinity,kubernetes.podspec-persistent-volume-claim,kubernetes.podspec-persistent-volume-write extensions. But in the official documentation, they are set to disabled by default (the official documentation explains that they are in the alpha stage and may have bugs). May I ask what bugs they may have, and has the latest version of knave already resolved these bugs?
The text was updated successfully, but these errors were encountered: