OSDOCS-5479: Documented the Welcome page for the 4.13 release notes do…#58640
OSDOCS-5479: Documented the Welcome page for the 4.13 release notes do…#58640JoeAldinger merged 1 commit intoopenshift:enterprise-4.13from
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@dfitzmau: This pull request references OSDOCS-5479 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
openshift-ci
Bot
added
the
size/XS
|
@dfitzmau: This pull request references OSDOCS-5479 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@dfitzmau: This pull request references OSDOCS-5479 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
dfitzmau
changed the title
|
@dfitzmau: This pull request references OSDOCS-5479 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
🤖 Updated build preview is available at: Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/15104 |
|
@dfitzmau: This pull request references OSDOCS-5479 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@dfitzmau: This pull request references OSDOCS-5479 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
dfitzmau
force-pushed
the
OSDOCS-5479
branch
2 times, most recently
from
3995ab9 to
e75f4fe
Compare
openshift-ci
Bot
added
size/M
dfitzmau
force-pushed
the
OSDOCS-5479
branch
2 times, most recently
from
1a5a6b0 to
e0eee63
Compare
openshift-merge-robot
added
the
needs-rebase
openshift-merge-robot
removed
the
needs-rebase
openshift-ci
Bot
added
size/L
|
@dfitzmau: This pull request references OSDOCS-5479 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@dfitzmau: This pull request references OSDOCS-5479 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
dfitzmau
force-pushed
the
OSDOCS-5479
branch
3 times, most recently
from
dbc808d to
0475550
Compare
|
@dfitzmau: This pull request references OSDOCS-5479 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
| - **xref:../applications/connecting_applications_to_services/understanding-service-binding-operator.adoc#understanding-service-binding-operator[Connect your workloads to backing services]**: The Service Binding Operator enables application developers to easily bind workloads with Operator-managed backing services by automatically collecting and sharing binding data with the workloads. The Service Binding Operator improves the development lifecycle with a consistent and declarative service binding method that prevents discrepancies in cluster environments. | ||
|
|
||
| - ** xref:../cli_reference/odo-important-update.adoc#odo-important_update[Use the developer CLI tool (`odo`)] **: | ||
| The `odo` CLI tool lets developers create single or multi-component applications easily and automates deployment, build, and service route configurations. It abstracts complex Kubernetes and {product-title} concepts, allowing you to focus on developing your applications. |
There was a problem hiding this comment.
Writer's note: Removed odo index items because they include a link that further links to a third-party application. Confirmed with Robert Kratky, but can request a more authentic response, if desired.
|
@dfitzmau: This pull request references OSDOCS-5479 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/label peer-review-needed |
openshift-ci
Bot
added
the
peer-review-needed
|
@dfitzmau: This pull request references OSDOCS-5479 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
| - **xref:../cicd/builds/understanding-image-builds.adoc#understanding-image-builds[Understand image builds]**: Choose from different build strategies (Docker, S2I, custom, and pipeline) that can include different kinds of source materials, such as Git repositories, local binary inputs, and external artifacts. You can follow examples of build types from basic builds to advanced builds. | ||
|
|
||
| - **xref:../openshift_images/index.adoc#overview-of-images[Create container images]**: A container image is the most basic building block in {product-title} (and Kubernetes) applications. Defining image streams lets you gather multiple versions of an image in one place as you continue its development. S2I containers let you insert your source code into a base container that is set up to run code of a particular type, such as Ruby, Node.js, or Python. | ||
| - **xref:../openshift_images/index.adoc#overview-of-images[Create container images]**: A container image is the most basic building block in {product-title} and Kubernetes applications. By defining image streams, you can gather multiple versions of an image in one place as you continue to development the image stream. With S2I containers, you can insert your source code into a base container. The base container is configured to run code of a particular type, such as Ruby, Node.js, or Python. |
There was a problem hiding this comment.
| - **xref:../openshift_images/index.adoc#overview-of-images[Create container images]**: A container image is the most basic building block in {product-title} and Kubernetes applications. By defining image streams, you can gather multiple versions of an image in one place as you continue to development the image stream. With S2I containers, you can insert your source code into a base container. The base container is configured to run code of a particular type, such as Ruby, Node.js, or Python. | |
| - **xref:../openshift_images/index.adoc#overview-of-images[Create container images]**: A container image is the most basic building block in {product-title} and Kubernetes applications. By defining image streams, you can gather multiple versions of an image in one place as you continue to develop the image stream. With S2I containers, you can insert your source code into a base container. The base container is configured to run code of a particular type, such as Ruby, Node.js, or Python. |
JoeAldinger
added
peer-review-done
|
#59688 pulls these changes into |
5 participants
IMPORTANT: Must check in with MBurke on May 10th to check if the Windows Operator is GA 4.13 ready (Commented out Understanding Windows container workloads index entry note for now)
NOTE: A merge conflict might occur because of this PR
OSDOCS-5479
Version(s):
4.13
Link to docs preview:
Preview
QE review:
Additional information: