You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the process of raising the NGINX Ingress Controller specific CRDs to v1, the TransportServer object was forgotten.
We need to remedy this.
Acceptance Criteria:
advance TransportServer versioning to v1
provide in-box backward compatibility for the current v1alpha1
provide in-box deprecation message about TransportServer v1alpha1 (log message, Event on object)
advance GlobalConfiguration versioning to v1
provide in-box backward compatibility for the current v1alpha1
provide in-box deprecation message about GlobalConfiguration v1alpha1 (log message, Event on object)
Remove previewpolicy flag (long deprecated and no longer in use)
### Tasks
- [x] Update CRDs in both `chats/nginx-ingress/crds/` and `deploy/crds.yaml`
- [x] Graduate TransportServer to V1
- [x] Graduate GlobalConfiguration to V1
- [x] Update documentation around graduation of TS and GC
- [x] Test deployments of TS and GC using Helm and deploy manually with `deploy/crds.yaml`
The text was updated successfully, but these errors were encountered:
@brianehlert should we create one for GlobalConfiguration as well?
We can extend this to cover both and have sub tasks for implementation if that is needed.
Or write a second one. It is simply about how the work is tracked.
During the process of raising the NGINX Ingress Controller specific CRDs to v1, the TransportServer object was forgotten.
We need to remedy this.
Acceptance Criteria:
The text was updated successfully, but these errors were encountered: