Skip to content

Commit 5cd39b8

Browse files
authored
Merge pull request #54234 from rh-max/srvls-remove-tp-notes
[SRVCOM-2213] Remove TP notes for features that went GA
2 parents a6fbdba + 7897e1c commit 5cd39b8

File tree

2 files changed

+0
-6
lines changed

2 files changed

+0
-6
lines changed

modules/serverless-admin-init-containers.adoc

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,6 @@
88

99
link:https://kubernetes.io/docs/concepts/workloads/pods/init-containers/[Init containers] are specialized containers that are run before application containers in a pod. They are generally used to implement initialization logic for an application, which may include running setup scripts or downloading required configurations. You can enable the use of init containers for Knative services by modifying the `KnativeServing` custom resource (CR).
1010

11-
:FeatureName: Init containers for Knative services
12-
include::snippets/technology-preview.adoc[leveloffset=+1]
13-
1411
[NOTE]
1512
====
1613
Init containers may cause longer application start-up times and should be used with caution for serverless applications, which are expected to scale up and down frequently.

modules/serverless-enabling-pvc-support.adoc

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,6 @@
88

99
Some serverless applications need permanent data storage. To achieve this, you can configure persistent volume claims (PVCs) for your Knative services.
1010

11-
:FeatureName: PVC support for Knative services
12-
include::snippets/technology-preview.adoc[leveloffset=+1]
13-
1411
.Procedure
1512

1613
. To enable Knative Serving to use PVCs and write to them, modify the `KnativeServing` custom resource (CR) to include the following YAML:

0 commit comments

Comments
 (0)