Comments (5)
Hi @msaustral
Do we need to install serving and eventing and operator?
You can install serving alone or eventing alone via yaml files. Or use the operator to install any of them.
For http2 support check this example. We don't support http2 autodetection yet, see #4283.
@pierDipi or @creydr could help with the Eventing questions? In general I think it is better to discuss Eventing at the corresponding repo.
from serving.
Hi @msaustral,
as @skonto said: in general it is better to discuss Eventing questions in the corresponding repo (e.g. knative/eventing) - or bring this question up in the #knative-eventing slack channel. Anyhow regarding your question:
what are the differences between them, refering to the functionality of knative? :
-Install a default Channel (messaging) layer
-Install a Broker layer
As said in here Channel and Subscriptions tend to involve a linear flow of events, e.g. via a Sequence or Parallel. The events are broadcasted to all Subscribers and there is no way to filter them.
Brokers and Triggers implement a routing-based model, where events are fed into a Broker and then dispatched intelligently based on the type or other event properties. So this allows filtering as well.
Depending on the Broker implementation (e.g. if you use the eventing-kafka-broker), you can gain more benefits as performance increases compared to a channel implementation (see knative/eventing#5558 (comment))
-Install optional Eventing extensions
The "default" Broker implementation in knative eventing does not persist the events (runs only in-memory). Thus it is not recommended to use in production. Therefor we offer different Broker implementations like eventing-kafka-broker, which use Apache Kafka as the backing technology.
I hope this helps. Feel free to reach out to us in Slack (#knative-eventing) or raise an issue in knative/eventing if the documentation is unclear.
from serving.
Hi sorry to bother
example:
we have a custom nginx container image that has the port 8443 and http2 enable
our dns server clouldflare and tls certificate is clouldflare server side full strict
to implement Knative can we just implement operator with serving?
to the tls we create the secret and then
apiVersion: serving.knative.dev/v1beta1
kind: DomainMapping
metadata:
name: xxxx.com
namespace: xxx-qa
spec:
ref:
name: web-xxxx
kind: Service
apiVersion: serving.knative.dev/v1
tls:
secretName: xxxx-com
apiVersion: networking.internal.knative.dev/v1alpha1
kind: ClusterDomainClaim
metadata:
name: xxxxx.com
spec:
namespace: xxx-qa
But we can not make it work
are we missing something?
from serving.
Hi, I think I managed to almost make it work, now we are getting this error on the custom domain
400 Bad Request
The plain HTTP request was sent to HTTPS port
nginx
This is because the traffic to the pod is being sent by http and not https need it to work http2
How can we make all internal traffic https using the server side cloudflare certificate and kourier?
from serving.
How can we make all internal traffic https using the server side cloudflare certificate and kourier?
The internal encryption feature is not there yet. You can read more about it here: knative/docs#5804.
from serving.
Related Issues (20)
- [failing] test/conformance/api/v1.TestRevisionTimeout HOT 7
- [failing] test/conformance/api/v1.TestRouteCreation HOT 1
- [failing] test/conformance/api/v1.TestServiceCreateAndUpdate HOT 1
- [failing] test/e2e.TestDestroyPodInflight HOT 3
- How to generate stat.pb.go file
- Looking for help: helloworld-go IngressNotConfigured HOT 4
- Unwanted scale-down during sustained load triggers an eventual explosion in replicas HOT 2
- [flaky] test/conformance/runtime.TestCmdArgs HOT 2
- [flaky] test/conformance/api/v1beta1.TestDomainMapping HOT 2
- Autoscaler create pods less than requests.
- [flaky] test/upgrade.TestServingUpgrades/Run/Steps/UpgradeWith/ServingHead HOT 2
- [flaky] pkg/activator/net: TestProbePodIPs
- Webhook Flake on Upgrade HOT 1
- [flaky] test/conformance/api/v1.TestServiceWithTrafficSplit HOT 2
- [flaky] test/conformance/api/v1.TestRevisionTimeout/writes_first_byte_before_timeout HOT 2
- Allow scale to zero to work when min-scale is greater than 0 HOT 2
- AWS External Load Balancer TLS Termination - generate 443 server rules when `default-external-scheme: https` is set HOT 2
- [Intermittent- RHEL cluster] - Knative activator pod is restarting continuously from crashloop back of with Liveness and Readiness probe failure HOT 1
- nodeSelector: validation failed: must not set the field(s): spec.template.spec.nodeSelector HOT 11
- Need help: KSVCs are not scaling down to zero HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from serving.