Remove latest tag and update env image URL to GHCR (#267)

* Remove latest tag.
Update environments images URL to point to GHCR.

Signed-off-by: Md Soharab Ansari <[email protected]>

* Resolve review comment

Signed-off-by: Md Soharab Ansari <[email protected]>

---------

Signed-off-by: Md Soharab Ansari <[email protected]>

Author: soharab-ic

content/en/blog/demystifying-fission-pool-manager.md

@@ -103,7 +103,7 @@ You can control the default pool size based on your needs. You can do so by sett
 For instance, the below code snippet with create a new Python environment with a poolsize of 1.
 
 ```bash
-$ fission env create --name python --version **3** --poolsize **1** --image ghcr.io/fission/python-env:latest
+$ fission env create --name python --version **3** --poolsize **1** --image ghcr.io/fission/python-env
 $ kubectl get pod -l environmentName**=**test
 ```
 

content/en/blog/fission-zapier-webhook/index.md

@@ -122,7 +122,7 @@ type: Opaque
 Create a Python environment
 
 ```bash
-fission environment create --name python --image ghcr.io/fission/python-env --builder ghcr.io/fission/python-builder:latest
+fission environment create --name python --image ghcr.io/fission/python-env --builder ghcr.io/fission/python-builder
 ```
 
 Create a zip archive as sample.zip archive by executing package.sh script

content/en/blog/fission_github_action.md

@@ -95,7 +95,7 @@ In the logs below, we can see that Fission Action applied the specs and the envi
 ```
 ### STARTED FissionCD 15:16:50Z
 
-Pulling image: gcr.io/github-actions-images/action-runner:latest
+Pulling image: gcr.io/github-actions-images/action-runner
 latest: Pulling from github-actions-images/action-runner
 169185f82c45: Pulling fs layer
 0ccde4b6b241: Pulling fs layer

content/en/blog/how-to-use-fission-functions-with-postgresql-database/index.md

@@ -122,13 +122,13 @@ After this create a docker image and push it to your Docker hub repository.
 Building the docker image for our custom Python environment. *(Replace the username with your actual username on Docker Hub.)*
 
 ``` bash
-docker build -t username/python-postgres:latest --build-arg PY_BASE_IMG=3.7-alpine -f Dockerfile .
+docker build -t username/python-postgres --build-arg PY_BASE_IMG=3.7-alpine -f Dockerfile .
 ```
 
 Pushing the docker image to Docker Hub registry:
 
 ``` bash
-docker push username/python-postgres:latest
+docker push username/python-postgres
 ```
 
 #### Source Package Setup
@@ -177,7 +177,7 @@ For this voting app, we will create `python environment`, `packages`, `fission f
 Creating the Python environment:
 
 ``` bash
-fission env create --name pythonsrc --image username/python-postgres --builder ghcr.io/fission/python-builder:latest
+fission env create --name pythonsrc --image username/python-postgres --builder ghcr.io/fission/python-builder
 ```
 
 Once the environment is ready, we create two Fission packages for `backend` and `frontend`
@@ -268,7 +268,7 @@ You can open a terminal and key in the all the following commands at once.
 
 ``` yaml
 fission spec init
-fission env create --name pythonsrc --image python-postgres --builder ghcr.io/fission/python-builder:latest --spec
+fission env create --name pythonsrc --image python-postgres --builder ghcr.io/fission/python-builder --spec
 fission package create --name backend-pkg --sourcearchive backend.zip --env pythonsrc --buildcmd "./build.sh" --spec
 fission fn create --name backend --pkg backend-pkg --entrypoint "backend.main" --spec
 fission route create --name backend --method POST --url /castvote --function backend --spec
@@ -281,7 +281,7 @@ This will create a `specs` folder with specs for each resource that is required
 
 ``` bash
 fission spec init
-fission env create --name pythonsrc --image atulinfracloud/python-postgres --builder ghcr.io/fission/python-builder:latest --spec
+fission env create --name pythonsrc --image atulinfracloud/python-postgres --builder ghcr.io/fission/python-builder --spec
 fission package create --name backend-pkg --sourcearchive backend.zip --env pythonsrc --buildcmd "./build.sh" --spec
 fission fn create --name backend --pkg backend-pkg --entrypoint "backend.main" --spec
 fission route create --name backend --method POST --url /castvote --function backend --spec

content/en/blog/observability-with-opentelemetry-datadog-in-fission/index.md

@@ -179,13 +179,13 @@ It should look like this: `RUN apk add --update --no-cache gcc python3-dev build
 Building the docker image for our custom Python environment. *(Replace the username with your actual username on Docker Hub.)*
 
 ``` dockerfile
-docker build -t username/python-opentelemetry:latest --build-arg PY_BASE_IMG=3.7-alpine -f Dockerfile .
+docker build -t username/python-opentelemetry --build-arg PY_BASE_IMG=3.7-alpine -f Dockerfile .
 ```
 
 Pushing the docker image to Docker Hub registry:
 
 ``` dockerfile
-docker push username/python-opentelemetry:latest
+docker push username/python-opentelemetry
 ```
 
 
@@ -194,7 +194,7 @@ docker push username/python-opentelemetry:latest
 Create Fission environment:
 
 ```bash
-fission env create --name pythonoptel --image username/python-opentelemetry --builder ghcr.io/fission/python-builder:latest
+fission env create --name pythonoptel --image username/python-opentelemetry --builder ghcr.io/fission/python-builder
 ```
 
 Create source package.
@@ -233,7 +233,7 @@ With this our custom Python environment is ready along with our Fission function
 
 ```bash
 fission spec init
-fission env create --name pythonoptel --image atulinfracloud/python-opentelemetry  --builder ghcr.io/fission/python-builder:latest --spec
+fission env create --name pythonoptel --image atulinfracloud/python-opentelemetry  --builder ghcr.io/fission/python-builder --spec
 fission package create --name fissionoptel-pkg --sourcearchive sample.zip --env pythonoptel --buildcmd "./build.sh" --spec
 fission fn create --name optel --pkg fissionoptel-pkg --entrypoint "sample.main" --spec
 ```

content/en/blog/serverless-twitter-bot-fission/index.md

@@ -122,7 +122,7 @@ Deploy the secret using `kubectl apply -f secrets.yaml`
 Create a Python environment
 
 ```bash
-fission environment create --name python --image ghcr.io/fission/python-env --builder ghcr.io/fission/python-builder:latest
+fission environment create --name python --image ghcr.io/fission/python-env --builder ghcr.io/fission/python-builder
 ```
 
 Create a zip archive as sample.zip archive by executing package.sh script

content/en/blog/url-shortener-fission-mongo-db/index.md

@@ -103,7 +103,7 @@ For this voting app, we will create `python environment`, `packages`, `fission f
 Create a Python environment
 
 ```bash
-fission environment create --name python --image ghcr.io/fission/python-env --builder ghcr.io/fission/python-builder:latest
+fission environment create --name python --image ghcr.io/fission/python-env --builder ghcr.io/fission/python-builder
 ```
 
 Once the environment is ready, we create two Fission packages for `backend` and `frontend`
@@ -214,7 +214,7 @@ You can open a terminal and key in the all the following commands at once.
 
 ``` yaml
 fission spec init
-fission environment create --name python --image ghcr.io/fission/python-env --builder ghcr.io/fission/python-builder:latest --spec
+fission environment create --name python --image ghcr.io/fission/python-env --builder ghcr.io/fission/python-builder --spec
 fission package create --name frontend-pkg --sourcearchive frontend.zip --env python --buildcmd "./build.sh" --spec
 fission package create --name backend-pkg --sourcearchive backend.zip --env python --buildcmd "./build.sh" --spec
 fission fn create --name frontend --pkg frontend-pkg --entrypoint "app.main" --spec
@@ -227,7 +227,7 @@ This will create a `specs` folder with specs for each resource that is required
 
 ``` bash
 fission spec init
-fission environment create --name python --image ghcr.io/fission/python-env --builder ghcr.io/fission/python-builder:latest --spec
+fission environment create --name python --image ghcr.io/fission/python-env --builder ghcr.io/fission/python-builder --spec
 fission package create --name frontend-pkg --sourcearchive frontend.zip --env python --buildcmd "./build.sh" --spec
 fission package create --name backend-pkg --sourcearchive backend.zip --env python --buildcmd "./build.sh" --spec
 fission fn create --name frontend --pkg frontend-pkg --entrypoint "app.main" --spec

content/en/blog/websocket-sample.md

@@ -123,7 +123,7 @@ fission spec init
 ```
 fission env create \
  --name=nodejs \
- --image=ghcr.io/fission/node-env:latest \
+ --image=ghcr.io/fission/node-env \
  --spec
 ```
 
@@ -155,7 +155,7 @@ fission httptrigger create \
 ```
 fission env create \
  --name=python \
- --image=ghcr.io/fission/python-env:latest \
+ --image=ghcr.io/fission/python-env \
  --spec
 ```
 

content/en/docs/usage/function/enabling-istio-on-fission.md

@@ -40,7 +40,7 @@ $ helm install --namespace $FISSION_NAMESPACE --set enableIstio=true --name isti
 Let's first create the environment for nodejs function we want to create:
 
 ```bash
-$ fission env create --name nodejs --image ghcr.io/fission/node-env:latest
+$ fission env create --name nodejs --image ghcr.io/fission/node-env
 ```
 
 Let's create a simple function with Node.js environment and a simple hello world example below:

content/en/docs/usage/function/environments.en.md

@@ -30,8 +30,8 @@ For more details on builder and packages, check out examples in [Functions]({{%
 
 ```bash
 $ fission env create --name python \
-                     --image ghcr.io/fission/python-env:latest \
-                     --builder ghcr.io/fission/python-builder:latest
+                     --image ghcr.io/fission/python-env \
+                     --builder ghcr.io/fission/python-builder
 ```
 
 ## Viewing environment information