Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Removal of mentions of Nodejs12 #15851

Merged
merged 7 commits into from Oct 20, 2022
Merged

Removal of mentions of Nodejs12 #15851

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
7650694
remove_nodejs12
Cortey Oct 19, 2022
2fabefb
remove_trash
Cortey Oct 19, 2022
bf1224f
remove_scaffold_md
Cortey Oct 19, 2022
6d2a29b
table
Cortey Oct 19, 2022
71f6cfe
fixtableformat
Cortey Oct 19, 2022
6ea7760
fix_typo
Cortey Oct 19, 2022
1c3bbf6
add_16
Cortey Oct 19, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 4 additions & 4 deletions components/function-controller/README.md
View file
Open in desktop
Expand Up @@ -28,7 +28,7 @@ To develop the component, use the formulae declared in the [generic](/common/mak
| **APP_LEADER_ELECTION_ENABLED** | Field that enables one instance of the Function Controller to manage the traffic among all instances | `false` |
| **APP_LEADER_ELECTION_ID** | Name of the ConfigMap that specifies the main instance of the Function Controller that manages the traffic among all instances | `serverless-controller-leader-election-helper` |
| **APP_KUBERNETES_BASE_NAMESPACE** | Name of the Namespace with the serverless configuration (such as runtime, Secret and service account for the Docker registry) propagated to other Namespaces | `kyma-system` |
| **APP_KUBERNETES_EXCLUDED_NAMESPACES** | List of Namespaces to which serverless configuration is not propagated | `istio-system,knative-eventing,kube-node-lease,kube-public,kube-system,kyma-installer,kyma-integration,kyma-system,natss,compass-system` |
| **APP_KUBERNETES_EXCLUDED_NAMESPACES** | List of Namespaces to which serverless configuration is not propagated | `istio-system,knative-eventing,kube-node-lease,kube-public,kube-system,kyma-installer,kyma-integration,kyma-system,natss,compass-system` |
| **APP_KUBERNETES_CONFIG_MAP_REQUEUE_DURATION** | Period of time after which the ConfigMap Controller refreshes the status of a ConfigMap | `1m` |
| **APP_KUBERNETES_SECRET_REQUEUE_DURATION** | Period of time after which the Secret Controller refreshes the status of a Secret | `1m` |
| **APP_KUBERNETES_SERVICE_ACCOUNT_REQUEUE_DURATION** | Period of time after which the ServiceAccount Controller refreshes the status of a ServiceAccount | `1m` |
Expand All @@ -39,14 +39,14 @@ To develop the component, use the formulae declared in the [generic](/common/mak
| **APP_FUNCTION_BUILD_REQUESTS_MEMORY** | Minimum amount of memory assigned to the Job to build a Function image. See [this](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/#meaning-of-cpu) document for available values. | `750mi` |
| **APP_FUNCTION_BUILD_LIMITS_CPU** | Maximum amount of CPU assigned to the Job to build a Function image. See [this](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/#meaning-of-cpu) document for available values. | `1` |
| **APP_FUNCTION_BUILD_LIMITS_MEMORY** | Maximum amount of memory assigned to the Job to build a Function image. See [this](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/#meaning-of-cpu) document for available values. | `1Gi` |
| **APP_FUNCTION_BUILD_RUNTIME_CONFIG_MAP_NAME** | Name of the ConfigMap that contains the runtime definition | `dockerfile-nodejs12` |
| **APP_FUNCTION_BUILD_RUNTIME_CONFIG_MAP_NAME** | Name of the ConfigMap that contains the runtime definition | `dockerfile-nodejs14` |
| **APP_FUNCTION_BUILD_EXECUTOR_ARGS** | List of arguments passed to the Kaniko executor | `--insecure,--skip-tls-verify,--skip-unused-stages,--log-format=text,--cache=true` |
| **APP_FUNCTION_BUILD_EXECUTOR_IMAGE** | Full name of the Kaniko executor image used for building Function images and pushing them to the Docker registry | `gcr.io/kaniko-project/executor:v0.22.0` |
| **APP_FUNCTION_BUILD_REPOFETCHER_IMAGE** | Full name of the Repo-Fetcher init container used for cloning repository for the Kaniko executor | `eu.gcr.io/kyma-project/function-build-init:305bee60` |
| **APP_FUNCTION_BUILD_MAX_SIMULTANEOUS_JOBS** | Maximum number of build jobs running simultaneously | `5` |
| **APP_FUNCTION_BUILD_MAX_SIMULTANEOUS_JOBS** | Maximum number of build jobs running simultaneously | `5` |
| **APP_FUNCTION_DOCKER_INTERNAL_SERVER_ADDRESS** | Internal server address of the Docker registry | `serverless-docker-registry.kyma-system.svc.cluster.local:5000` |
| **APP_FUNCTION_DOCKER_REGISTRY_ADDRESS** | External address of the Docker registry | `registry.kyma.local` |
| **APP_FUNCTION_TARGET_CPU_UTILIZATION_PERCENTAGE** | Average CPU usage of all the Pods in a given Deployment. It is represented as a percentage of the overall requested CPU. If the CPU consumption is higher or lower than this limit, HorizontalPodAutoscaler (HPA) scales the Deployment and increases or decreases the number of Pod replicas accordingly. | `50` |
| **APP_FUNCTION_TARGET_CPU_UTILIZATION_PERCENTAGE** | Average CPU usage of all the Pods in a given Deployment. It is represented as a percentage of the overall requested CPU. If the CPU consumption is higher or lower than this limit, HorizontalPodAutoscaler (HPA) scales the Deployment and increases or decreases the number of Pod replicas accordingly. | `50` |

#### The Webhook uses these environment variables:

Expand Down
2 changes: 1 addition & 1 deletion docs/01-overview/main-areas/serverless/svls-02-from-code-to-function.md
View file
Open in desktop
Expand Up @@ -6,7 +6,7 @@ Pick the programming language for the Function and decide where you want to keep

## Runtimes

Functions support multiple languages by using the underlying execution environments known as runtimes. Currently, you can create both Node.js (12 & 14) and Python (3.9) Functions in Kyma.
Functions support multiple languages by using the underlying execution environments known as runtimes. Currently, you can create both Node.js (14 & 16) and Python (3.9) Functions in Kyma.

>**TIP:** See [sample Functions](../../../05-technical-reference/svls-01-sample-functions.md) for each available runtime.

Expand Down
2 changes: 1 addition & 1 deletion docs/01-overview/main-areas/serverless/svls-04-development-toolkit.md
View file
Open in desktop
Expand Up @@ -10,6 +10,6 @@ To start developing your first Functions, you need:
- [**kubectl**](https://kubernetes.io/docs/reference/kubectl/kubectl/), the Kubernetes command-line tool, for running commands against clusters
- Development environment of your choice:
- **Kyma CLI** to easily initiate inline Functions or Git Functions locally, run, test, and later apply them on the clusters
- **Node.js** (v12 or v14) or **Python** (v3.9)
- **Node.js** (v14 or v16) or **Python** (v3.9)
- **IDE** as the source code editor
- **Kyma Dashboard** to manage Functions and related workloads through the graphical user interface
2 changes: 1 addition & 1 deletion ...echnical-reference/00-configuration-parameters/svls-02-environment-variables.md
View file
Open in desktop
Expand Up @@ -17,7 +17,7 @@ Every runtime provides its own unique environment configuration which can be rea
| **FUNC_PORT** | `8080` | The right port, a server listens to. |
| **SERVICE_NAMESPACE** | | The Namespace where the right Function exists on a cluster. |
| **KUBELESS_INSTALL_VOLUME** | `/kubeless` | Full path to volume mount with users source code. |
| **FUNC_RUNTIME** | | The name of the actual runtime. Possible values: `python39`, `nodejs12`, `nodejs14`, `nodejs16`. |
| **FUNC_RUNTIME** | | The name of the actual runtime. Possible values: `python39`, `nodejs14`, `nodejs16`. |
| **TRACE_COLLECTOR_ENDPOINT** | `http://tracing-jaeger-collector.kyma-system.svc.cluster.local:4318/v1/traces` | Full address of the Open-Telemetry Trace Collector. |
| **JAEGER_SERVICE_ENDPOINT** | `http://tracing-jaeger-collector.kyma-system.svc.cluster.local:14268/api/traces` | **Deprecated in 2.8** Full address of the Jaeger service. |
| **PUBLISHER_PROXY_ADDRESS** | `http://eventing-publisher-proxy.kyma-system.svc.cluster.local/publish` | Full address of the Publisher Proxy service. |
Expand Down
2 changes: 1 addition & 1 deletion docs/05-technical-reference/svls-04-git-source-type.md
View file
Open in desktop
Expand Up @@ -2,7 +2,7 @@
title: Git source type
---

Depending on a runtime you use to build your Function (Node.js 12, Node.js 14, or Python 3.9), your Git repository must contain at least a directory with these files:
Depending on a runtime you use to build your Function (Node.js 14, Node.js 16, or Python 3.9), your Git repository must contain at least a directory with these files:

- `handler.js` or `handler.py` with Function's code
- `package.json` or `requirements.txt` with Function's dependencies
Expand Down
4 changes: 2 additions & 2 deletions docs/05-technical-reference/svls-08-function-specification.md
View file
Open in desktop
@@ -1,8 +1,8 @@
---
z---
title: Function's specification
---

Serverless in Kyma allows you to create Functions in both Node.js (v12 & v14) and Python (v3.9). Although the Function's interface is unified, its specification differs depending on the runtime used to run the Function.
Serverless in Kyma allows you to create Functions in both Node.js (v14 & v16) and Python (v3.9). Although the Function's interface is unified, its specification differs depending on the runtime used to run the Function.

## Signature

Expand Down