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
Copy file name to clipboardExpand all lines: website/content/en/docs/faqs/_index.md
+42Lines changed: 42 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -265,6 +265,48 @@ If your bundle is too large, there are a few things you can try:
265
265
* Reducing the number of [CRD versions][k8s-crd-versions] supported in your Operator by deprecating and then removing older API versions. It is a good idea to have a clear plan for deprecation and removal of old CRDs versions when new ones get added, see [Kubernetes API change practices][k8s-api-change]. Also, refer to the [Kubernetes API conventions][k8s-api-convention].
266
266
* Reduce the verbosity of your API documentation. (We do not recommend eliminating documenting the APIs)
267
267
268
+
## How can I update dependencies for an unsupported release image?
269
+
270
+
The Operator-SDK community releases updated images for supported
271
+
releases. If you are using an older version of Operator-SDK, sometimes
272
+
the dependencies will need to be updated in the images. For users in
273
+
this situation we recommend updating to the latest version. If this is
274
+
not possible, users can build and push their own versions of any of the
0 commit comments