Revision 7d3c3a7c8637ae46ffd79c2066096fe74078a47c authored by Joe Stringer on 30 September 2020, 22:13:35 UTC, committed by Sebastian Wicki on 06 October 2020, 08:58:44 UTC
[ upstream commit b71cf0d0fff4d17f788a01c55affd79715731d46 ] Due to an extra `v` in the branch name, this script would fail with: $ ~/git/cilium/contrib/release/start-release.sh v1.6.12 128 fatal: 'origin/vv1.6' is not a commit and a branch 'pr/prepare-v1.6.12' cannot be created from it Signal ERR caught! Traceback (line function script): 62 main /home/joe/git/cilium/contrib/release/start-release.sh Fix it. While we're at it, update the instructions at the end for next steps, since there's also now a `submit-backport.sh` script to send the PR from the CLI. Signed-off-by: Joe Stringer <joe@cilium.io> Signed-off-by: Paul Chaignon <paul@cilium.io>
1 parent fbf7d4a
USERS.md
Who is using Cilium?
====================
Sharing experiences and learning from other users is essential. We are
frequently asked who is using a particular feature of Cilium to get in
contact with other users to share experiences and best-practices. While the
[Cilium Slack community](https://cilium.herokuapp.com/) allows users to
get in touch, it can be challenging to find users of a particular feature
quickly.
The following is a directory of users to help identify users of individual
features. The users themselves directly maintain the list.
Adding yourself as a user
-------------------------
If you are using Cilium, please consider adding yourself as a user with a quick
description of your use case by opening a pull request to this file and adding
a section describing your usage of Cilium. If you are open to others contacting
you about your use of Cilium on Slack, add your Slack nick as well.
N: Name of user (company or individual)
D: Description
U: Usage of features
L: Link with further information (optional)
Q: Contacts available for questions (optional)
Example entry:
* N: Cilium Example User Inc.
D: Cilium Example User Inc. is using Cilium for scientific purposes
U: ENI networking, DNS policies, ClusterMesh
Q: @slacknick1, @slacknick2
Requirements to be listed
-------------------------
* You must represent the user listed. Do *NOT* add entries on behalf of
other users.
* There is no minimum deployment size but we request to list permanent
deployments only, i.e., no demo or trial deployments. Commercial or
production use is not required. A well-done home lab setup can be equally
interesting as a large-scale commercial deployment.
Users (Alphabetically)
----------------------
* N: Adobe, Inc.
D: Adobe's Project Ethos uses Cilium for multi-tenant, multi-cloud clusters
U: L3/L4/L7 policies
L: https://youtu.be/39FLsSc2P-Y
* N: CENGN - Centre of Excellence in Next Generation Networks
D: CENGN is using Cilium in multiple clusters including production and development clusters (self-hosted k8s, On-premises)
U: L3/L4/L7 network policies, Monitoring via Prometheus metrics & Hubble
L: https://www.youtube.com/watch?v=yXm7yZE2rk4
Q: @rmaika @mohahmed13
* N: Datadog
D: Datadog is using Cilium in AWS (self-hosted k8s)
U: ENI Networking, Service load-balancing, Encryption
Q: @lbernail, @roboll
* N: Palantir Technologies Inc.
D: Palantir is using Cilium as their main CNI plugin in AWS (self hosted k8s).
U: ENI networking, L3/L4 policies, FQDN based policy, FQDN filtering
Q: ungureanuvladvictor
* N: Rapyuta Robotics.
D: Rapyuta is using cilium as their main CNI plugin. (self hosted k8s)
U: CiliumNetworkPolicy, Hubble, Service Load Balancing.
Q: @Gowtham
* N: Sportradar
D: Sportradar is using Cilium as their main CNI plugin in AWS (using kops)
U: L3/L4 policies, Hubble, BPF NodePort, CiliumClusterwideNetworkPolicy
Q: @Eric Bailey, @Ole Markus
* N: uSwitch
D: uSwitch is using Cilium in AWS for all their production clusters (self hosted k8s)
U: ClusterMesh, CNI-Chaining (with amazon-vpc-cni-k8s)
Q: @jirving
* N: Trip.com
D: Trip.com is using Cilium in their production clusters (self-hosted k8s, On-premises and AWS)
U: ENI Networking, Service load-balancing, Direct routing (via Bird)
L: https://ctripcloud.github.io/cilium/network/2020/01/19/trip-first-step-towards-cloud-native-networking.html
Q: @ArthurChiao
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...