**Describe something that is unclear or not documented and needs a documentation update
in Logs with loki catalog， helm install loki stack， and provide a config.yaml。but not specified a version, so i follow tutorial document get a lots of bug, the loki-grafana secrets is not have grafana config key, since the loki-grafana-437cxx pod is notReady status.
the config.yaml is not fine for latest version，it cant get response for scarpes pod, the pod is error with **Readiness probe failed: HTTP probe failed with statuscode: 500**. in actually, im so unaided.

example env create contains --poolsize argument but not --version, so poolsize is ignored.

fission env create --name pythonsrc --image fission/python-env:latest \
                     --builder fission/python-builder:latest \
                     --mincpu 40 --maxcpu 80 \
                     --minmemory 64 --maxmemory 128 \
                     --poolsize 2

should read:

                     --poolsize 2 --version 3

The documentation has a lot of example code. Most examples are not complete, some of it are (incomplete) spec files, other examples are JavaScript or Python code. I find it helpful to have fully working examples so I don't have to piece bits of documentation example code together for a working example.

Having all source code for an function in the docs is less then ideal (hence why all examples are incomplete). I would propose to have a link to the file on Github when there is a code example so the complete file and accompanying files for a function can be looked at.

Here are examples by Google.

Observed via https://www.brokenlinkcheck.com/

Reference:

• https://blog.fission.io/fission_github_action/

Fission's Python documentation doesn't talk about customizing the image on this page. As a developer when I'm following this guide, I need to know that in some scenarios, I need to use a custom image without which the function will not execute.

There has a to be a note on this page that mentions these scenarios, so that the developer can follow the guide accordingly and setup the environment.

Windows cli can now be installed via Scoop.

scoop install fission-cli

https://fission.codes/blog/wallet-stack/

Currently, we use /posts/ as a prefix to all blog URLs we should use /blog instead to maintain better directory structure and sitemap.

We need to add some documentation which helps to decide what is the right value for poolsize in poolmgr executortype.
If the poolsize is less than required, we get errors like error posting to getting service for function: context deadline exceeded if there are many requests.
If the poolsize is more than required, we will end up utilizing more resources.

Fission supports a lot of languages, but the documentation has examples in a single language. The introduction to writing a function has an example in JavaScript, while the section about configmaps has an example in Python.

I would propose to have examples in all the available languages. Google Developer Documentation has a great example with Firebase Cloud Firestore. Functions and Fission are new concepts for lots of developers, having documentation with in the language they are familiar with, makes it a bit easier to get started with Fission.

Templates already have support for it. It is for example used on the installation guide page.

mqtrigger is not able to pick the messages from the configured Kafka Cluster, even though the Kafka Cluster is up and running fine and other clients can produce the message to that Kafka Cluster.
We dont see any logs in that pod also so it becomes increasingly tough to debug the mqtrigger.
We should have some steps documented in this page that explain how can we debug if mqtrigger is not able to pick the Kafka messages and call fission function.

We should have default community health files, such as CONTRIBUTING and CODE_OF_CONDUCT. Default files will be used for any public repository owned by the account that does not contain its own file of that type.

References:

• GitHub Doc
• Kubernetes
• Tinkerbell

Related Issues:

• Broken link - Code of conduct
• Missing LICENSE

Doc Page: https://fission.io/docs/usage/languages/python/#modifying-the-runtime-environment-image

The git clone directory is out-of-date. Pulling the fission repo will not give you the environments sub-directory as indicated in the docs. Instead, users should pull the environment repo.

Proposed changes:

• Change git clone https://github.com/fission/fission to git clone https://github.com/fission/environments
• Change cd fission/environments/python to cd environments/python

Some areas in the documentation that can be improved based:

General Issues

• Architecture sidebar menu is missing optional components, it should list all the core and optional components, currently it shows only the core components.
• https://fission.io/docs/concepts/ -> Environment -> can change the anchor text from "here" to "Fission Environments". Something like: Check out our complete list of Fission Environments.
• We should add a full architectural diagram of Fission on the Architecture page - will add more value to the page
• The text "Brief Intro", "Diagram" on every page should be removed, provides no extra info to the user nor for SEO

Individual Page Specific changes

• Controller: The text "Kubernetes CRDs" - can be linked to https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/ - will provide better context to the reader
• Executor: PoolManager, NewDeploy - link to the relevant places on the page
• Function Pod: Fetcher & Environment Container - descriptions can be moved above the image
• Builder Manager: the page mentions "fission-builder" namespace, however we don't have any page listing all the namespaces that fission creates. We can create a new page with all fission namespaces - something like this -> https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/#viewing-namespaces
• Builder Pod: Fetcher & Builder container - descriptions can be moved above the image
• StorageSVC: can rename to Storage Service which has better readability and replace the same at all occurrences
• Logger: DaemonSets - can link to https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/ - - will provide better context to the reader
• Logger: links can be updated, for eg.: under Function Pod, we mention StorageSVC, but we have not mentioned it earlier. Hence we should link this to StorageSVC page or provide a small intro here.
• Kubewatcher: "Kubewatcher link to issue #64" - either add the link to the issue or remove the text.

Fission/Kubernetes version

$ fission --version
$ kubectl version

Kubernetes platform (e.g. Google Kubernetes Engine)

Describe the bug

To Reproduce
Visit the website

Expected result

Loads and displays properly

Actual result
Fails to load the file: https://fission.io/scss/main.min.3a11f6677f03a755cbda7bb8bd7a2d08ffe0ceba6bada3a2a1423500743622ce.css

Screenshots/Dump file

$ fission support dump

Additional context

How can I expose the grafana port so that I can visit the webpage from external?

The documentation needs to clearly lay out how to get the API Documentation using OpenAPI and how to access it from a client such as curl or postman

So, I was going through the fission.io website today when I came across this issue.

The Ham menu doesn't work when clicked. I'm attaching a clip of the issue below.

I'm on a Ubuntu 20.04 LTS version

Documentation of all Fission Custom Resources similar to Fission CLI

We can consider using project https://github.com/elastic/crd-ref-docs for automation CRD docs generation.

We need docs for GCP Pub Sub connector under Keda Trigger docs

Documentation URL: contributing : https://github.com/fission/fission.io/blob/11c77d5b84a9ae31e61e1aa5a174ccbaba6d2099/CONTRIBUTING.md

go1.15.15go1.15.15 npm 7.5.2
Hugo Static Site Generator v0.80.0/extended linux/amd64 BuildDate: 2021-07-18T09:31:51Z (debian 0.80.0-6+b5)

Error: add site dependencies: load resources: loading templates: "/home/steve/projects/fission.io/layouts/shortcodes/readfile.html:27:1": parse failed: template: shortcodes/readfile.html:27: unexpected unclosed action in parenthesized pipeline

$ git status
On branch main
Your branch is up to date with 'origin/main'.

nothing to commit, working tree clean

$ go version
go version go1.15.15 linux/amd64
$ hugo version
Hugo Static Site Generator v0.80.0/extended linux/amd64 BuildDate: 2021-07-18T09:31:51Z (debian 0.80.0-6+b5)
$ npm --version
7.5.2

$ hugo server
Error: add site dependencies: load resources: loading templates: "/home/foo/projects/fission.io/layouts/shortcodes/readfile.html:27:1": parse failed: template: shortcodes/readfile.html:27: unexpected unclosed action in parenthesized pipeline

A progressive web application is a type of application software delivered through the web, built using common web technologies including HTML, CSS, and JavaScript. It is intended to work on any platform that uses a standards-compliant browser, including both desktop and mobile devices. Progressive Web Apps (PWAs) allow developers to deliver an app-like experience to the user.

I would like to work on the issue, in case you don't want PWA support feel free to close the issue! Looking forward to working contribute to one of the best Org out there ⚡️

Currently the documentation for environments varies from environment to environment. Most of the environments lack info on common questions users have: How do I setup this environment? Which version should I use? What is the latest version of environment? Does it have a builder? Does it support functionality X?

We should ensure that the documentation is sufficient enough to help the user with these questions, which otherwise confuse the user at runtime and lead to pressure on the support.

I think it would help if we have some sort of a template or checklist what should be in the environment documentation. From the top of my head we should consider it to constitute of the following should be in there:

• Cut-and-paste examples of most recent version
• A table indicating what functionality is supported (builder, V2, V3, etc)
• Links to examples
• Build instructions
• Some text on the functions./usage: how to set response code, how to get headers, body, and query params. What happens on exceptions?
• Known issues/FAQ
• Changelog on changes made to the environment

The current search on site is not very intuitive with GCS search, we should try to switch to algolia instead.

We also need to check if we can be enabled autocomplete search.

Docsy Hugo also provides an offline search option, need to check if it can work for us.

• Create docs on various modules
  • Draw some sequence diagrams of common flows (e.g. builder, function cold start, spec apply, etc.)
• Label issues that are good for beginners: easy and low-enough priority. Avoid working on them so other people can.
• Take another look at contributors guide and see what needs to be improved.

for this portion of the documentation for installing prometheus montioring,

"Install Prometheus and Grafana with the release name fission-metrics."
should the directions say for the release name to be "prometheus" instead?

If I am doing just as described in docs then after execution of this command

fission package create --sourcearchive demo-src-pkg.zip --env pythonsrc --buildcmd "./build.sh"

I am getting following error:
Build Logs:
error building source package: error starting cmd: fork/exec ./build.sh: no such file or directory
Error building deployment package: Internal error - 500 Internal Server Error
However running same command without passing --buildcmd option everything is working fine

I'd love to see a blog on how to add a language to Fission. I'm trying to get this working with SBCL (Steel Bank Common Lisp) and would to see a good blog post on how to add something like SBCL into Fission.

curl -v https://fission.io

• About to connect() to fission.io port 443 (#0)
• Trying 75.2.60.5...

stuck at connecting

Users often get confused if they can use environment variables with Fission functions.
Based on yes/no we should document it accordingly and provide samples/details.

In the observability/opentelemetry installation commands for the jaeger-operator installation are provided.
From the current documentation

kubectl create -n observability -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/crds/jaegertracing.io_jaegers_crd.yaml
kubectl create -n observability -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/service_account.yaml
kubectl create -n observability -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/role.yaml
kubectl create -n observability -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/role_binding.yaml
kubectl create -n observability -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/operator.yaml

At github jaegertracing/jaeger-operator/master a deploy directory isn't there anymore. In the latest tag where the deploy directory is available is v1.28.0.

I accommodate this for me as the following :

JAEGER_VERSION=v1.28.0
kubectl create -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/$JAEGER_VERSION/deploy/crds/jaegertracing.io_jaegers_crd.yaml # <2>
kubectl create -n observability -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/$JAEGER_VERSION/deploy/service_account.yaml
kubectl create -n observability -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/$JAEGER_VERSION/deploy/role.yaml
kubectl create -n observability -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/$JAEGER_VERSION/deploy/role_binding.yaml
kubectl create -n observability -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/$JAEGER_VERSION/deploy/operator.yaml

The jaeger-operator install documentation https://www.jaegertracing.io/docs/1.29/operator/ points to a version 1.29 which not exits on the tags on github. The jaeger doc shows the same commands the in the fission docs provided.

We should have a License to this repository.
https://help.github.com/articles/licensing-a-repository/

Describe the bug

Currently, I can not access the fission.io website. There may be something wrong with the certificates.

To Reproduce

Visit the fission.io website.

Expected result

It would be nice to navigate the site again and read the documentation, etc.

Actual result
Currently, I get an connection error within firefox and chrome.

I am trying to setup a function that would trigger when a message was added to azure storage queue. I was looking at the documentation here https://docs.fission.io/docs/triggers/message-queue-trigger/ how ever, I dont find details about how the queue's connection string / credentials can be passed for the messagequeuetrigger to listen.

https://fission.io/docs/installation/env_vars/#fission-router-address section should be removed as it is no longer supported.

Primary marketing image on https://fission.io/ has a typo and looks extremely unprofessional. Specifically, terminal line two.

Line: fission function create --funtion
Solution: --funtion should be spelled as --function

Source Images on GitHub:

https://github.com/fission/fission.io/blob/514835fd5a713557857ab6e4c6bbdd3781bbdf76/static/images/body-img-1.svg

https://github.com/fission/fission.io/blob/514835fd5a713557857ab6e4c6bbdd3781bbdf76/static/images/body-img-1.png

It used to be possible to apply certain modifications (specifically, in this case, nodeSelector clauses - being able to use those is essential in mixed-architecture clusters to ensure that correct binary images and functions are supplied to each node, or in clusters where functions require particular peripheral hardware not present on all nodes) to the builder and runtime pods created by fission, in this format:

apiVersion: fission.io/v1
kind: Environment
metadata:
  creationTimestamp: null
  name: binary-amd64
  namespace: default
spec:
  builder:
    command: build
    image: fission/binary-builder:v1.11.2
    podspec:
      nodeSelector:
        kubernetes.io/arch: amd64
  imagepullsecret: ""
  keeparchive: false
  poolsize: 1
  resources: {}
  runtime:
    image: fission/binary-env:1.11.2
    podspec:
      nodeSelector:
        kubernetes.io/arch: amd64
  version: 3

But now doing so fails, since the containers: element is mandatory in the new Environment CRD. Unfortunately, while this much is discoverable from the documentation at https://doc.crds.dev/github.com/fission/fission/fission.io/Environment/v1 , it's not at all obvious how to use the podspec clause (and its new mandatory element) to achieve what the above used to, or indeed to get a working spec at all. (I have not yet managed it.)

Could we have an example showing how to use podspec, and possibly also some common usages of it in the primary documentation?

We need docs for Rabbitmq connector under Keda Trigger docs

I believe, here is a small typo:

fission function run-container provides required options to run an **exiting** container image as a Fission function.

It should be existing instead of exiting?

How do I allow users with the "devs" role to create functions without giving them full admin rights? What are the resources and verbs I have to use for the fission namespace in order to grant access to use fission in our cluster? It would be great to have an example in the documentation. I am sure I am not the only one who has asked this question.

Minion already has a way to notify a NATS queue on object addition/deletion etc. It would be good to build a small working prototype for using that for invoking a Fission function (Reference: https://docs.min.io/docs/minio-bucket-notification-guide.html)

Hi, Please change below url as it has been deprecated for Loki
helm repo add grafana https://grafana.github.io/helm-charts/
helm install -n monitoring --create-namespace loki grafana/loki-stack

For grafana installation, we should use official helm repo
helm repo add grafana https://grafana.github.io/helm-charts/
helm repo update
helm upgrade --install grafana grafana/grafana --create-namespace -n grafana
Accessing Grafana UI
To get login credentials of grafana
Default user is “admin”
For password, run the below command

kubectl get secret --namespace grafana grafana -o jsonpath="{.data.admin-
password}" | base64 --decode

To access UI, run below command

kubectl port-forward svc/grafana -n grafana 3000:80

Document the details of Authentication & Authorization for Fission and functions so the user knows what needs to be done.