2.0.0
We are happy to announce the release of Kyma 2.0! This major release brings a lot of fresh air to the project: we simplified and improved many areas, and also provided some brand new features, such as Kyma Dashboard. Read on to find out what Kyma 2.0 has to offer!
CAUTION: In this release, authentication and authorization methods in Kyma have changed. Before upgrading to Kyma 2.0, read the Migration Guide.
See the overview of all changes in this release:
API Exposure
Exposing workloads on custom domains
Kyma 2.0 allows you to expose Istio workloads using custom, user-managed domains. In previous Kyma versions, the only supported scenario was to use the main Kyma domain for API exposure. Now, provided you own a domain, you can expose any Kyma-hosted workload using your domain. In addition, a TLS certificate can be automatically generated for you. You can have multiple workloads using multiple custom domains. Read how to use a custom domain to expose a service for details.
Application Connectivity
New way to reach registered services
Kyma 2.0 brings some fresh air to the Application Connectivity area. There is now a possibility to call an external registered service without creating ServiceInstances and binding them to the workload. Central Application Gateway is a new component responsible for this part.
In the future, this will be the default way of creating Application-related flows, as Service Catalog will be removed and the option to create ServiceInstances and bindings will go away. While we will support the existing flows for some time, we highly recommend you try out the new, simplified approach now.
Application Connectivity improvements
We are reducing the complexity and resource usage of the whole Application Connectivity area. For this reason, two new components were introduced:
- Central Application Gateway
- Central Application Connectivity Validator
The changes allow us to drop per-application deployments (Gateways and Validators). We are also looking at detaching Application Connector from Service Catalog and Rafter.
With these changes, some of the components, such as Application Operator, will become obsolete. We will remove them in the following releases. This, however, will have no effect on the existing functionality.
CLI
Switch from Minikube to k3d
With Kyma 2.0, we switched the local Kubernetes tool from Minikube to k3d, which allows for a faster and more lightweight installation. The steps needed to set up a local and remote cluster are now the same.
Revamped way of installation
We fundamentally improved and simplified the way to install Kyma, phasing out the Kyma Installer component. With this change, Kyma is up to date with the current Kubernetes security, authorization, and identity standards. Cluster admins can restrict user permissions as desired; the permissions are evaluated based on the kubeconfig. There is no god-mode Service Account within the cluster anymore, and the Kyma installation is now entirely client-side.
The commands for installation have been updated as well:
- The
deploy
command replaces theinstall
andupgrade
commands. - The
undeploy
command replaces theuninstall
command.
Values instead of configuration overrides
Instead of the deprecated --override
flag, we now use the deploy
command to change Kyma settings. With the --values-file
flag, you can change Kyma settings by providing a plain YAML file. Alternatively, you can provide values inline with the --value
flag. Learn more in Change Kyma Settings.
The kyma test
command deprecated
With Kyma 2.0, the test framework changed and now testing happens entirely client-side. As of this release, the kyma test
command is deprecated.
The kyma console
command replaced with kyma dashboard
Starting from this release, to open the graphical user interface for Kyma, use the kyma dashboard
command. The kyma console
command is now deprecated.
Eventing
NATS Operator replaced with NATS Helm chart
In Kyma 2.0, we removed the NATS Operator and its CRDs from Eventing. Instead, we now use the NATS Helm chart. This has no impact on the user, since all configurations have been mapped to the new NATS Helm chart.
Kyma Dashboard
Kyma Console replaced with new technology
Kyma 2.0 brings you a new user interface. Kyma Dashboard, based on the Busola project, replaces the old Kyma Console.
Kyma Dashboard is decoupled from the Kyma cluster. It is not part of the initial Kyma installation, but you can add it to the cluster manually, or run it on your local machine using Kyma CLI.
Moreover, we removed the Console Backend Service and now we connect with the Kubernetes API directly.
Kyma Dashboard features
Kyma Dashboard provides many new features:
- You can work with multiple clusters, switch between them, and add external clusters.
- The new deep linking functionality allows you to easily jump between your apps and the related resources.
- For better accessibility, you can choose from the light, dark, and high contrast themes.
New resources views
You can now view all Kyma and most Kubernetes resources in the left navigation panel of Kyma Dashboard. These are the new resources views:
- Service Accounts
- Cluster Overview > Nodes
- Jobs
- Cron Jobs
- Stateful Sets
- Daemon Sets
- Gateways
- Issuers
- Certificates
- DNS Providers
- DNS Entries
Easier resource creation
Kyma Dashboard also allows you to easily create new resources:
- Roles
- Role Bindings
- Service Accounts
- Deployment
- Cron Jobs
- Jobs
- Config Maps
- Secrets
- Issuers
- Certificates
- DNS Providers
- DNS Entries
- Replica Sets
You can create these resources directly in the UI by going to the appropriate resource view in the left navigation panel.
Observability
Authentication for Grafana, Kiali, and Jaeger UIs
With the deprecation of Dex, authentication for the Observability user interfaces is now much simpler and more consistent. Grafana, Kiali, and Jaeger UIs are no longer exposed by default. Instead, you have the flexibility to set up your preferred OIDC provider for each service.
As a result, all users are logged on anonymously and see the same UI. If you prefer a user-specific configuration for Grafana UI, use the Grafana log-in solution and switch off the OAuth proxy.
Read our documentation to learn how to expose services securely.
Improved security for logs in Kyma Dashboard
Logs displayed in Kyma Dashboard are now based on the Kubernetes API server. This way, Loki is no longer exposed to the external network, which reduces the attack vector.
Containerd support
With the update of Fluent Bit to version 1.8, we activated the new multiline support feature and configured support for Docker and containerd.
Prometheus mTLS
By enabling Prometheus mTLS, you can improve the security in your Service Mesh and keep the strict mTLS mode for custom metrics. You don't have to weaken the authentication policy when you are scraping workloads deployed in the Service Mesh. Learn more in Enable mTLS for custom metrics.
Observability services updated
With this release, we have also refreshed Observability a bit (no pun intended). Fluent Bit has been upgraded to the latest version 1.8.10, Grafana got a minor upgrade to 7.5.11, Loki has been upgraded to 2.2.1, and OAuth2 Proxy was bumped to version 7.2.0.
For more information, read the release notes for Fluent Bit, Grafana, Loki, and OAuth2 Proxy.
Security
Native Kubernetes authentication in Kyma
With 2.0, we untangled authentication concepts in Kyma. We removed the complexity of having a built-in authentication component (Dex) and proxies to the Kubernetes API server (API Server Proxy and Console Backend Service). We decided to use plain Kubernetes authentication and authorization options:
With this change, we were able to remove many service accounts with high privileges, and several other attack vectors that could lead to unauthorized access to your cluster resources - for example, static users in Dex configuration - admin@kyma.cx
or kubeconfig pointing to apiserver-proxy
with a token valid for several hours.
See the full list of removed authentication and authorization components:
- API Server Proxy
- Console Backend Service
- Dex
- IAM Kubeconfig Service
- Permission Controller
The list is quite long, but it doesn't affect most of the production use cases. The components were used mainly for exposing Kyma UI in the development/standalone mode (static users). For such use cases, we provide the refactored, better and faster Kyma Dashboard.
Ory Oathkeeper without Dex
With Kyma 2.0, the Dex component becomes deprecated. Therefore, Ory Oathkeeper will no longer use Dex to verify JWT tokens. Existing API Rules that have a JWT access strategy defined must be enriched with an individual jwks_url parameter pointing to a custom OpenID Connect-compliant identity provider.
Serverless
Support for Python 3.8 deprecated
In this release, we deprecate support for Python 3.8, and in the upcoming releases, we will remove it from the list of supported runtimes. Kyma already has Python 3.9 available in Serverless, and we recommend that you configure all your Python 3.8 Functions to run on the Python 3.9 runtime.
Service Management
Service Catalog deprecation update
As we announced the deprecation of Service Catalog in Kyma 1.23 Dhahran, in Kyma 2.0 we recommend using service operators for Service Management. These are the examples of service operators provided by hyperscale cloud providers that you can use:
Note that with the Service Catalog removal, it will no longer be possible to manage the existing hyperscalers' instances using Kyma, and the migration for these instances will not be provided. You will only be able to manage them on the hyperscaler's side. All the existing Secrets with credentials to services will stay in the cluster and will still be injected to your deployments and Functions.
The Service Catalog removal will also affect Application Connectivity in Kyma. Service Catalog objects will not be used anymore, and both ServiceInstances and ServiceBindings will not be required.
Website
New landing page
The Kyma website now has a brand new landing page. The new content gives you an overview of what Kyma is, what its main features are, and what problems it solves.
New documentation structure
We restructured the Kyma documentation quite significantly in the 2.0 release. We no longer divide the left navigation based on Kyma components. Instead, it's structured based on the tasks you would normally face when using Kyma. We split rather long documents into shorter, more digestible chunks. On top of that, the collapsible tabs in the left navigation panel group the content into categories that help you find answers to your questions faster.
Roadmap removed
We removed the Roadmap section from the Kyma website. Refer to Kyma GitHub issues to find the details about planned features.
2.0.0 (2021-12-07)
Application Connector
- #12800 Bump Application Connector images (@franpog859)
- #12786 Simplify App Conn tutorials some more (@majakurcius)
- #12721 Tests for CRUD operations on application services (@mvshao)
- #12465 Adjust Application Connectivity docs to Kyma 2.0, pt.2 (@majakurcius)
- #12470 Fix Application Mapping CRD (@franpog859)
- #12396 Update the Runtime Agent guide to reflect changes to Kyma installation (@majakurcius)
- #12294 Deleted deprecated Runtime API in Connector Service (@mvshao)
- #12324 Remove Application Connector CRDs from deprecated location (@franpog859)
- #12322 Update Application CRD (@franpog859)
- #12181 Add Central Gateway URL to the Application CustomResource using Application Registry (@franpog859)
- #12148 Migrate Application Connector requirements.yaml to Chart.yaml (@rafalpotempa)
- #12116 Fix fast integration tests with central app gateway failing (@franpog859)
- #11952 Update CODEOWNERS with Central Application Connectivity charts (@rafalpotempa)
- #11881 Upgrade dependencies in Application Operator (@rafalpotempa)
- #11846 Refactor central-application-connectivity-validator cache sync controller. (@everesio)
- #11845 Update the Application Connector chart documentation (@majakurcius)
- #11676 Add Central Connectivity Validator fast integration tests (@rafalpotempa)
- #11778 Fix a typo in the central_application_connectivity_validator parameter name (@majakurcius)
- #11728 Add liveness and readiness probes to application-operator (@skhalash)
- #11631 Move Central Application Gateway and Central Connectivity Validator to kyma-system namespace (@franpog859)
- #11623 Replace satori/go.uuid with google/uuid in Application Registry (@rafalpotempa)
- #11591 Clean Application Operator dependencies up (@franpog859)
Serverless
- #12759 Replace PR tags for the serverless and the rafter components (@pPrecel)
- #12339 Remove minikube from svls (@NHingerl)
- #12079 Fix the
serverless-long
test (@pPrecel) - #11980 Replace all PR tags in the serverless chart (@pPrecel)
- #11968 Disable buffering in python runtimes (@pPrecel)
- #11879 Add OAuth2 secured API Rule to fast-integration tests (@tgorgol)
- #11697 Allow for easy back-channel communication from function to eventing backend (@pPrecel)
- #11752 Document easy back-channel communication from function to eventing backend (@pPrecel)
- #11744 Add missing liveness/readiness probes to serverless pods (@skhalash)
- #11708 Fix Serverless admission webhook (@tgorgol)
- #11666 Update wookiees codeowners (@pPrecel)
- #11612 Migrate serverless admission webhooks to v1 (@tgorgol)
Eventing
- #12801 Bump eventing-controller image (@pxsalehi)
- #12797 Bump publisher proxy image (@pxsalehi)
- #12753 fix issues found by various linters (@k15r)
- #12648 Allow using different mock namespaces (@pxsalehi)
- #12723 update nats server to 2.6.5 (@k15r)
- #12701 remove nats-operator (@k15r)
- #12567 Add a new Condition for BEB Webhook callback status (@radufa)
- #12677 update eventing-controller dependency in event-publisher-proxy (@k15r)
- #12699 Removed unused reloader and exporter from NATS helm chart (@mfaizanse)
- #12637 Update Eventing images (@marcobebway)
- #12616 bump go version (@pxsalehi)
- #12312 fix the eventingReady status change right after the backend switch (@VladislavPaskar)
- #12553 Rename commander to subscription manager in eventing-controller (@pxsalehi)
- #12549 Small improvements to the eventing-controller dev setup (@pxsalehi)
- #12535 React to OAuth2 secret changes in the Eventing controller (@pxsalehi)
- #12441 Update event-subscriber dependencies (@pxsalehi)
- #12434 Update event publisher proxy dependencies (@pxsalehi)
- #12432 Update Eventing controller dependencies (@pxsalehi)
- #12420 Fix CVE-2021-25741 for Eventing components (@marcobebway)
- #12397 Add metric tests for eventing (@pxsalehi)
- #12189 Read eventTypePrefix from ConfigMap (@marcobebway)
- #12315 Upgrade CE-SDK to 2.5.0 in eventing-controller (@radufa)
- #12318 Upgrade CE-SDK to 2.5.0 in event-publisher-proxy (@radufa)
- #12283 address linting issues (@k15r)
- #12154 Fix event-publisher-proxy ha issue (@radufa)
- #12119 Add tests for CE dispatching on NATS (@radufa)
- #12170 Nats-operator image: upgrade to alpine:3.14.2 (@radufa)
- #12115 Move in-cluster eventing sub-test to the fixture (@pxsalehi)
- #12078 Upgrade nats-server to 2.2.4 (@radufa)
- #12085 Extend existing in-cluster eventing test in fast-integration (@pxsalehi)
- #12075 Fix nats-operator (@radufa)
- #12063 Add "check-code" for local publisher-proxy development (@radufa)
- #12056 Add lint for the local eventing-controller development (@radufa)
- #12050 Reconcile Kyma subscription if APIRule is updated/deleted (@pxsalehi)
- #12045 Cleanup the code referring to the OAuth usage in BEB subscriptions (@radufa)
- #12006 Fix event multiplexer pattern for NATS (@radufa)
- #11993 Rely on OAuth2Client CR in the Helm chart (@pxsalehi)
- #11920 Fix nats-operator (@marcobebway)
- #11807 Recreate BEB subscription if it was deleted from BTP side (@radufa)
- #11733 Use timeout on channel read (@pxsalehi)
- #11621 Use Nats queue subscriptions (@radufa)
- #11419 Update fast-integration test to support switching Eventing backends (@marcobebway)
- #11651 Enhance Eventing controller logs (@marcobebway)
- #11634 Optimze HTTP header access in test (@themue)
- #11655 Use the same version of the OAuth2Client CRD as installation (@pxsalehi)
- #11610 Deduplicate subscription filters (@pxsalehi)
- #11527 Remove isBEBEnabled flag (@marcobebway)
- #11574 Update external crd for eventing controller (@pxsalehi)
- #11507 Dynamic oauth2client creation (@pxsalehi)
Security
- #12785 Adjust Ory replicaCount with the HPA in the Helm templates (@cnvergence)
- #12700 Move dependencies section to the Chart definition in Oathkeeper (@mjakobczyk)
- #12611 Replace the
registry
component (@pPrecel) - #12618 Update Ory oath2clients CRD (@cnvergence)
- #12577 Bump Ory components to the latest versions (@cnvergence)
- #12580 Upgrade serverless components (@pPrecel)
- #12578 upgrade kaniko version (@pPrecel)
- #12571 Remove unused
minio_client
image from thevalues
file (@pPrecel) - #12570 Update minio image (@pPrecel)
- #12506 added kyma disclaimer to istio svc & po (@strekm)
- #12559 Fix security issues in the context of the rafter image (@pPrecel)
- #12313 Updated auth doc (@mmitoraj)
- #12420 Fix CVE-2021-25741 for Eventing components (@marcobebway)
- #11834 remove jobs from certificates component (@strekm)
- #11861 Replacing Dex with Ory Hydra login and consent app in api-gateway tests (@cnvergence)
- #11890 Bump text and websocket packages (@dariadomagala)
- #11883 Add health probe endpoint to api-gateway (@cnvergence)
- #11881 Upgrade dependencies in Application Operator (@rafalpotempa)
- #11623 Replace satori/go.uuid with google/uuid in Application Registry (@rafalpotempa)
- #11535 Change insensitive terms into their inclusive alternatives (@cnvergence)
Service Mesh
- #12640 Remove unnecessary helm values from profiles in istio-configuration component (@Tomasz-Smelcerz-SAP)
- #12506 added kyma disclaimer to istio svc & po (@strekm)
- #12361 Move deprecated Istio proxy config (@cnvergence)
- #12092 authproxy must not forward host header for istio routing (@a-thaler)
- #12055 kiali not working with istio 1.11 - update kiali to 1.38.1 (@a-thaler)
- #11979 Istio-configuration helm chart fixes (@cnvergence)
- #11965 Upgrade Istio to 1.11.1 (@cnvergence)
- #11964 Upgrade Istio Installer to 1.11.1 (@cnvergence)
- #11702 IstioOperator Helm chart for Kyma 2.0 (@cnvergence)
- #11689 Clean-up default and not-used values of Istio Operator (@cnvergence)
- #11560 upgrade Kiali to 1.36 (@a-thaler)
Installation
- #12352 Cleaning cluster-users (@strekm)
- #12220 bump gce-proxy in ORY chart (@strekm)
- #11834 remove jobs from certificates component (@strekm)
- #11810 Fix Kyma operator (@cnvergence)
- #11809 Helm wait fix (@cnvergence)
Monitoring
- #12792 Improved docu for mTLS scrape setup (@a-thaler)
- #12760 Restore Istio PeerAuthentications (with strict mode) (@skhalash)
- #12749 disable alertmanager grafana dashboard if alertmanager is deactivated (@a-thaler)
- #12739 Add permissive mTLS policy for Fluent Bit (@skhalash)
- #12724 update oauth2-proxy to 7.2 (@a-thaler)
- #12659 removed resourceSelector workaround from monitoring chart (@a-thaler)
- #12395 Add higher level of retries for monitoring tests (@shorim)
- #12369 Fix communication between prometheus and alertmanager (@skhalash)
- #12340 fixed problems with extraPort rendering (@a-thaler)
- #12300 cleanup for observability charts (@a-thaler)
- #12278 Remove axios-retry (@shorim)
- #12043 Update Prometheus Alertmanager to Version 0.23.0 (@jeremyharisch)
- #12028 security update of several images (@a-thaler)
- #11771 made kubelet alert rule resilient to muliple kubelet scrapeconfigs (@a-thaler)
- #11735 Add liveness and readiness probes to prometheus operator (@skhalash)
- #11712 Add readiness probes to OAuth2 proxies (@skhalash)
- #11594 Upgrade Grafana to latest Apache licensed version (@elchead)
Logging
- #12704 Document Loki and Prometheus limits (@NHingerl)
- #12739 Add permissive mTLS policy for Fluent Bit (@skhalash)
- #12660 update fluent-bit to 1.8.10 (@a-thaler)
- #12630 Increase maxUnavailable count for DaemonSets (@chrkl)
- #12554 enable containerd support in fluent-bit, enable new multiline feature (@a-thaler)
- #12510 update fluent-bit to 1.8.9 (@a-thaler)
- #12500 Update threshold for audit events (@shorim)
- #12463 update fluent-bit to 1.8.8 (@a-thaler)
- #12300 cleanup for observability charts (@a-thaler)
- #12278 Remove axios-retry (@shorim)
- #12232 removed trailing spaces in fluent-bit config (@a-thaler)
- #12133 updated fluent-bit to 1.8.7 (@a-thaler)
- #12083 have lokis removeKeys attribute overridable (@a-thaler)
- #12028 security update of several images (@a-thaler)
- #11983 upgrade to fluent-bit 1.8 (@a-thaler)
- #11947 Move telemetry operator to the rest of the charts (@skhalash)
- #11901 telemetry helm chart (@shorim)
- #11680 added a psp specific for fluent-bit (@a-thaler)
- #11657 Restrict fluent-bit pod permissions (@elchead)
- #11577 upgrade to loki 2.2.1 (@a-thaler)
Tracing
- #12724 update oauth2-proxy to 7.2 (@a-thaler)
- #12300 cleanup for observability charts (@a-thaler)
- #12280 Enabled non-mtls support for pushing traces (@a-thaler)
- #12194 kiali cannot reach jaeger - enable sidecar for kiali (@a-thaler)
- #12092 authproxy must not forward host header for istio routing (@a-thaler)
- #11712 Add readiness probes to OAuth2 proxies (@skhalash)
- #11677 fixed jaeger CRD schema (@a-thaler)
Console
- #11898 Remove PR image for CBS (@dariadomagala)
- #11890 Bump text and websocket packages (@dariadomagala)
Documentation
- #12799 Fix the titles of the "Revoke a client cert" tutorials (@majakurcius)
- #12795 Fix the link to the migration script (@klaudiagrz)
- #12794 remove 404 link (@NHingerl)
- #12654 Add Kyma 2.0 migration guide (@mmitoraj)
- #12792 Improved docu for mTLS scrape setup (@a-thaler)
- #12786 Simplify App Conn tutorials some more (@majakurcius)
- #12784 Include email scope in the oauth2-proxy setup documentation (@kwiatekus)
- #12704 Document Loki and Prometheus limits (@NHingerl)
- #12747 Update the k3d version in Prerequisites for Kyma installation and Get Started (@majakurcius)
- #12737 Fix a broken link (@klaudiagrz)
- #12716 correct steps for Busola Dashboard in Get Started (@grego952)
- #12662 change in glossary.md and quick-install.md (@grego952)
- #12465 Adjust Application Connectivity docs to Kyma 2.0, pt.2 (@majakurcius)
- #12546 Add a caution note (@mmitoraj)
- #12574 Fix a typo (@klaudiagrz)
- #12520 Fix broken links (@mmitoraj)
- #12458 Updated docs about certificates (@mmitoraj)
- #12490 Fix Eventing architecture documentation (@alexandra-simeonova)
- #12425 Fix broken link (@NHingerl)
- #12364 first draft fritzbox troubleshooting (@NHingerl)
- #12485 Change "Tutorials" into "Developer Tutorials" (@klaudiagrz)
- #12477 update k3d docs: revert to v4 (@NHingerl)
- #12313 Updated auth doc (@mmitoraj)
- #12379 Fix typo in Kyma docs (@alexandra-simeonova)
- #12359 K3d update: v5 (@NHingerl)
- #12357 remove docker image docs with minikube (@NHingerl)
- #12351 Remove the definite article from components names (@mmitoraj)
- #12350 Update the commands to run Kyma Dashboard in the documentation (@majakurcius)
- #12339 Remove minikube from svls (@NHingerl)
- #12334 Fix dead links (@alexandra-simeonova)
- #12331 remove tutorial to use Kyma CLI as kubectl plugin (@NHingerl)
- #12299 add sub-headlines (@NHingerl)
- #12277 fix broken links from kyma-governance-nightly (@NHingerl)
- #12276 review CLI docs (@NHingerl)
- #12273 kyma delete is now undeploy (@NHingerl)
- #12250 Fixed dead links (@mmitoraj)
- #12022 Fix a broken link (@klaudiagrz)
- #11960 Fix note on Kyma versions (@alexandra-simeonova)
- #11929 Add note about Kyma version support (@alexandra-simeonova)
- #11848 Remove the Migration Guide for Kyma 1.23 (@majakurcius)
- #11845 Update the Application Connector chart documentation (@majakurcius)
- #11843 fix broken link (@NHingerl)
- #11671 Fix links to Gardener documentation (@majakurcius)
- #11632 Fix links returning 404 error (@alexandra-simeonova)
- #11568 Use latest minio image (@tgorgol)
CI
- #12648 Allow using different mock namespaces (@pxsalehi)
- #10839 Improve event-publisher-proxy build performance (@Halamix2)
Core and Supporting
Committers: 69
- Adam Wałach (@adamwalach)
- Adrian Stobbe (@elchead)
- Aleksandra Simeonova (@alexandra-simeonova)
- Andreas Thaler (@a-thaler)
- Andrzej Pankowski (@Cortey)
- Arkadiusz Galwas (@akgalwas)
- Benjamin Lindner (@lindnerby)
- Benjamin Somhegyi (@ebensom)
- Christoph Kleineweber (@chrkl)
- Christoph Voigt (@voigt)
- Damian Badura (@dbadura)
- Daniel Gospodinow (@danielgospodinow)
- Daria Domagała (@dariadomagala)
- Filip Strózik (@pPrecel)
- Franciszek Pogodziński (@franpog859)
- Frank Mueller (@themue)
- Friedrich (@FriedrichWilken)
- Jan Wozniak (@wozniakjan)
- Jeremy Harisch (@jeremyharisch)
- Johannes Veicht (@veichtj)
- Kamil Kasperski (@Ressetkk)
- Kamil Sputo (@ksputo)
- Karol Szwaj (@cnvergence)
- Klaudia Grzondziel (@klaudiagrz)
- Korbinian Stoemmer (@k15r)
- Krystian Cieślik (@crabtree)
- Krzysztof (@kwiatekus)
- Magda Stręk (@strekm)
- Maja Kurcius (@majakurcius)
- Marcin Szwed (@szwedm)
- Marco Bebway (@marcobebway)
- Mariusz Szymański (@Maladie)
- Martin F (@gabel)
- Małgorzata Świeca (@mmitoraj)
- Michal Budzyn (@everesio)
- Michał Jakóbczyk (@mjakobczyk)
- Mohamed Elsayed (@moelsayed)
- Mostafa Shorim (@shorim)
- Muhammad Faizan (@mfaizanse)
- Nina Hingerl (@NHingerl)
- Patryk Strugacz (@werdes72)
- Piotr (@pbochynski)
- Piotr Halama (@Halamix2)
- Piotr Jasiak (@jasiu001)
- Piotr Kopec (@piotrkpc)
- Piotr Miśkiewicz (@piotrmiskiewicz)
- Piotr Wawrzyńczyk (@Wawrzyn321)
- Pooya Salehi (@pxsalehi)
- Przemyslaw Golicz (@koala7659)
- Radu Fantaziu (@radufa)
- Rafał Jankowski (@rJankowski93)
- Rafał Potempa (@rafalpotempa)
- Rakesh Garimella (@rakesh-garimella)
- Raymond Pinto (@raypinto)
- Sayan Hazra (@sayanh)
- Stanislav Khalash (@skhalash)
- Thandayuthapani (@thandayuthapani)
- Tobias Schuhmacher (@tobiscr)
- Tomasz Gorgol (@tgorgol)
- Tomasz Smelcerz (@Tomasz-Smelcerz-SAP)
- Wojciech Sołtys (@Sawthis)
- @VladislavPaskar
- @dariusztutaj
- @grego952
- @hamdymoussa
- @ralikio
- @szymon-nex
- marcin witalis (@m00g3n)
- mvshao (@mvshao)