openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

OSDOCS-3746 OSDK 1.22 project migration

Browse Source
This commit is contained in:
Michael Ryan Peter
2022-06-17 17:24:33 -04:00
committed by openshift-cherrypick-robot
parent 49b041cda3
commit 0a89385e4e
8 changed files with 488 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
operators/operator_sdk/ansible/osdk-ansible-updating-projects.adoc Normal file
View File

@@ -0,0 +1,31 @@
:_content-type: ASSEMBLY
[id="osdk-ansible-updating-projects"]
= Updating projects for newer Operator SDK versions
include::_attributes/common-attributes.adoc[]
:context: osdk-ansible-updating-projects
:osdk_ver: 1.22.0
:osdk_ver_n1: 1.16.0
:product-version-n1: 4.10
toc::[]
{product-title} {product-version} supports Operator SDK {osdk_ver}. If you already have the {osdk_ver_n1} CLI installed on your workstation, you can update the CLI to {osdk_ver} by xref:../../../operators/operator_sdk/osdk-installing-cli.adoc#osdk-installing-cli[installing the latest version].
However, to ensure your existing Operator projects maintain compatibility with Operator SDK {osdk_ver}, update steps are required for the associated breaking changes introduced since {osdk_ver_n1}. You must perform the update steps manually in any of your Operator projects that were previously created or maintained with {osdk_ver_n1}.
include::modules/osdk-updating-projects.adoc[leveloffset=+1]
[id="additional-resources_osdk-ansible-upgrading-projects"]
[role="_additional-resources"]
== Additional resources
* xref:../../../operators/operator_sdk/osdk-pkgman-to-bundle.adoc#osdk-pkgman-to-bundle[Migrating package manifest projects to bundle format]
* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.10/html-single/operators/index#osdk-upgrading-v1101-to-v1160_osdk-upgrading-projects[Upgrading projects for Operator SDK v1.16.0]
* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.9/html/operators/developing-operators#osdk-upgrading-v180-to-v1101_osdk-upgrading-projects[Upgrading projects for Operator SDK v1.10.1]
* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.8/html/operators/developing-operators#osdk-upgrading-v130-to-v180_osdk-upgrading-projects[Upgrading projects for Operator SDK v1.8.0]
:!osdk_ver:
:!osdk_ver_n1:
:!product-version-n1:

31
operators/operator_sdk/golang/osdk-golang-updating-projects.adoc Normal file
View File

@@ -0,0 +1,31 @@
:_content-type: ASSEMBLY
[id="osdk-golang-updating-projects"]
= Updating Go-based Operator projects for newer Operator SDK versions
include::_attributes/common-attributes.adoc[]
:context: osdk-golang-updating-projects
:osdk_ver: 1.22.0
:osdk_ver_n1: 1.16.0
:product-version-n1: 4.10
toc::[]
{product-title} {product-version} supports Operator SDK {osdk_ver}. If you already have the {osdk_ver_n1} CLI installed on your workstation, you can update the CLI to {osdk_ver} by xref:../../../operators/operator_sdk/osdk-installing-cli.adoc#osdk-installing-cli[installing the latest version].
However, to ensure your existing Operator projects maintain compatibility with Operator SDK {osdk_ver}, update steps are required for the associated breaking changes introduced since {osdk_ver_n1}. You must perform the update steps manually in any of your Operator projects that were previously created or maintained with {osdk_ver_n1}.
include::modules/osdk-updating-projects.adoc[leveloffset=+1]
[id="additional-resources_osdk-upgrading-projects-golang"]
[role="_additional-resources"]
== Additional resources
* xref:../../../operators/operator_sdk/osdk-pkgman-to-bundle.adoc#osdk-pkgman-to-bundle[Migrating package manifest projects to bundle format]
* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.10/html-single/operators/index#osdk-upgrading-v1101-to-v1160_osdk-upgrading-projects[Upgrading projects for Operator SDK 1.16.0]
* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.9/html/operators/developing-operators#osdk-upgrading-v180-to-v1101_osdk-upgrading-projects[Upgrading projects for Operator SDK v1.10.1]
* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.8/html/operators/developing-operators#osdk-upgrading-v130-to-v180_osdk-upgrading-projects[Upgrading projects for Operator SDK v1.8.0]
:!osdk_ver:
:!osdk_ver_n1:
:!product-version-n1:

31
operators/operator_sdk/helm/osdk-helm-updating-projects.adoc Normal file
View File

@@ -0,0 +1,31 @@
:_content-type: ASSEMBLY
[id="osdk-helm-updating-projects"]
= Updating Helm-based projects for newer Operator SDK versions
include::_attributes/common-attributes.adoc[]
:context: osdk-helm-updating-projects
:osdk_ver: 1.22.0
:osdk_ver_n1: 1.16.0
:product-version-n1: 4.10
toc::[]
{product-title} {product-version} supports Operator SDK {osdk_ver}. If you already have the {osdk_ver_n1} CLI installed on your workstation, you can update the CLI to {osdk_ver} by xref:../../../operators/operator_sdk/osdk-installing-cli.adoc#osdk-installing-cli[installing the latest version].
However, to ensure your existing Operator projects maintain compatibility with Operator SDK {osdk_ver}, update steps are required for the associated breaking changes introduced since {osdk_ver_n1}. You must perform the update steps manually in any of your Operator projects that were previously created or maintained with {osdk_ver_n1}.
include::modules/osdk-updating-projects.adoc[leveloffset=+1]
[id="additional-resources_osdk-helm-upgrading-projects"]
[role="_additional-resources"]
== Additional resources
* xref:../../../operators/operator_sdk/osdk-pkgman-to-bundle.adoc#osdk-pkgman-to-bundle[Migrating package manifest projects to bundle format]
* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.10/html-single/operators/index#osdk-upgrading-v1101-to-v1160_osdk-upgrading-projects[Upgrading projects for Operator SDK 1.16.0]
* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.9/html/operators/developing-operators#osdk-upgrading-v180-to-v1101_osdk-upgrading-projects[Upgrading projects for Operator SDK v1.10.1]
* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.8/html/operators/developing-operators#osdk-upgrading-v130-to-v180_osdk-upgrading-projects[Upgrading projects for Operator SDK v1.8.0]
:!osdk_ver:
:!osdk_ver_n1:
:!product-version-n1:

31
operators/operator_sdk/helm/osdk-hybrid-helm-updating-projects.adoc Normal file
View File

@@ -0,0 +1,31 @@
:_content-type: ASSEMBLY
[id="osdk-hybrid-helm-updating-projects"]
= Updating Hybrid Helm-based projects for newer Operator SDK versions
include::_attributes/common-attributes.adoc[]
:context: osdk-hybrid-helm-updating-projects
:osdk_ver: 1.22.0
:osdk_ver_n1: 1.16.0
:product-version-n1: 4.10
toc::[]
{product-title} {product-version} supports Operator SDK {osdk_ver}. If you already have the {osdk_ver_n1} CLI installed on your workstation, you can update the CLI to {osdk_ver} by xref:../../../operators/operator_sdk/osdk-installing-cli.adoc#osdk-installing-cli[installing the latest version].
However, to ensure your existing Operator projects maintain compatibility with Operator SDK {osdk_ver}, update steps are required for the associated breaking changes introduced since {osdk_ver_n1}. You must perform the update steps manually in any of your Operator projects that were previously created or maintained with {osdk_ver_n1}.
include::modules/osdk-updating-projects.adoc[leveloffset=+1]
[id="additional-resources_osdk-hybrid-helm-upgrading-projects"]
[role="_additional-resources"]
== Additional resources
* xref:../../../operators/operator_sdk/osdk-pkgman-to-bundle.adoc#osdk-pkgman-to-bundle[Migrating package manifest projects to bundle format]
* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.10/html-single/operators/index#osdk-upgrading-v1101-to-v1160_osdk-upgrading-projects[Upgrading projects for Operator SDK 1.16.0]
* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.9/html/operators/developing-operators#osdk-upgrading-v180-to-v1101_osdk-upgrading-projects[Upgrading projects for Operator SDK v1.10.1]
* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.8/html/operators/developing-operators#osdk-upgrading-v130-to-v180_osdk-upgrading-projects[Upgrading projects for Operator SDK v1.8.0]
:!osdk_ver:
:!osdk_ver_n1:
:!product-version-n1:

30
operators/operator_sdk/osdk-upgrading-projects.adoc
View File

@@ -1,30 +0,0 @@
:_content-type: ASSEMBLY
[id="osdk-upgrading-projects"]
= Updating projects for newer Operator SDK versions
include::_attributes/common-attributes.adoc[]
:context: osdk-upgrading-projects
:osdk_ver: v1.16.0
:osdk_ver_n1: v1.10.1
:product-version-n1: 4.9
toc::[]
{product-title} {product-version} supports Operator SDK {osdk_ver}. If you already have the {osdk_ver_n1} CLI installed on your workstation, you can update the CLI to {osdk_ver} by xref:../../operators/operator_sdk/osdk-installing-cli.adoc#osdk-installing-cli[installing the latest version].
However, to ensure your existing Operator projects maintain compatibility with Operator SDK {osdk_ver}, update steps are required for the associated breaking changes introduced since {osdk_ver_n1}. You must perform the update steps manually in any of your Operator projects that were previously created or maintained with {osdk_ver_n1}.
include::modules/osdk-updating-v1101-to-v1160.adoc[leveloffset=+1]
[id="additional-resources_osdk-upgrading-projects"]
[role="_additional-resources"]
== Additional resources
* xref:../../operators/operator_sdk/osdk-pkgman-to-bundle.adoc#osdk-pkgman-to-bundle[Migrating package manifest projects to bundle format]
* link:https://docs.openshift.com/container-platform/4.9/operators/operator_sdk/osdk-upgrading-projects.html#osdk-upgrading-v180-to-v1101_osdk-upgrading-projects[Upgrading projects for Operator SDK v1.10.1]
* link:https://docs.openshift.com/container-platform/4.8/operators/operator_sdk/osdk-upgrading-projects.html#osdk-upgrading-v130-to-v180_osdk-upgrading-projects[Upgrading projects for Operator SDK v1.8.0]
//Consider updating this during the 4.10 to 4.11 version scrub.
:!osdk_ver:
:!osdk_ver_n1:
:!product-version-n1: