cloud-native
Here are 744 public repositories matching this topic...
-
Updated
Feb 19, 2021 - Go
Any hover effects doesn't properly applied to all header elements (top line with cluster name and cluster menu). It seems that something placed on top of them and covers most of their height.
https://user-images.githubusercontent.com/9607060/108056014-cd186a00-7061-11eb-8ac0-5d01e206e636.mp4
ActorAdapter will ignore null message with "Adapter function returned null which is not valid as an .."
However, this seems not be documented. For instance, scaladoc/javadoc of pipeToSelf could mention it as well as any other place where adapters are used.
-
Updated
Feb 14, 2021 - Go
-
Updated
Feb 9, 2021
-
Updated
Feb 19, 2021 - Go
-
Updated
Feb 19, 2021 - Go
-
Updated
Feb 11, 2021 - Shell
-
Updated
Feb 19, 2021
Description
This follows a discussion on Zulip[1].
To generate the DDL for JPA and/or Panache entities, I can use the schema-generation.scripts properties in the persistence.xml file as follow:
<property name="javax.persistence.schema-generation.scripts.action" value="drop-and-create"/>
<property name="javax.persistence.schema-generation.scripts.create-target" value="create.
Local PV (device) provisioner leaves a stale BDC in the following case:
- On PVC request, creates a BDC
- If the system doesn't have a matching BD, then PVC request keeps retrying, and so does the NDM operator that keeps retrying
- Now if the user deletes the PVC, then Local PV (device) provisioner doesn't get the trigger to process delete, as there was no PVC.
This causes the stale BDC
What problem are you trying to solve?
When injecting linkerd into manifests that use the SSF protocol it would be nice to be able to do so via am cli flag
just like
linkerd inject --skip-inbound-ports=3306 --skip-outbound-ports=3306 -for this setting
Any alternatives you've considered?
Via pipelines the linkerd properties would be set in the manifests already
-
Updated
Feb 4, 2021 - Go
-
Updated
Feb 9, 2021 - Scala
I find a solution in the forum
https://kubesphere.com.cn/forum/d/3384-kubespheredevopsdotnet-core
But it is too trouble to use , and waste much time to set up it .
So any plan for including it to the nodes of devops flow.
Extending the work in yugabyte/yugabyte-db#6772, it'll be helpful to also show in the http://yb-master:7000/tablet-server-clocks view, for each yb-tserver, the RTT time between the yb-tserver and yb-master leader.
This will give a quick indication of how geographically dispersed the nodes in the system are.
Minor annoyance department, but still.
Expected Behavior
Switching between version in the docs should jump between versions of the page currently viewed.
Actual Behavior
Changing version always take you to the introduction page.
-
Updated
Sep 29, 2020 - Go
-
Updated
Feb 18, 2021 - Java
-
Updated
Feb 2, 2021 - Makefile
What would you like to be added/modified:
To improve project stability, we need more tests to cover corner cases.
And the code coverage is around 50% currently, we need to add more tests to improve it.
To improve case coverage, we may need a list of cases to track the work.
For code coverage, simply check bef
chaos-daemon doesn't have any authentication mechanism, which means any client in the cluster could modify the iptables and ipset config / cause stress / inject IO latency for nearly all the pods.
gRPC with server side SSL/TLS authentication is enough. However, it may break the chaosctl (which is definitely an evidence for the risk), or we need to distribute the certificate to it (or it can
-
Updated
Feb 17, 2021 - Go
-
Updated
Feb 18, 2021 - Python
-
Updated
Feb 18, 2021 - Go
-
Updated
Feb 19, 2021 - Java
Task
Convert CI to GitHub Actions
Context
Travis is removing its free tier for OSS projects, so this should be built with GitHub Actions instead, which is not going to add additional cost.
I would expect this to be one of the easier projects to convert given that Docker isn't used in the build.
See also:
https://github.com/mvdan/github-actions-golang
https://github.com/ac
Improve this page
Add a description, image, and links to the cloud-native topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the cloud-native topic, visit your repo's landing page and select "manage topics."
Next line returns 200 as status https://github.com/Kong/kong/blob/c817fada7a514d84f6e0aab7461605c71bf3a841/kong/plugins/cors/handler.lua#L13
Internet says it should return 204:
Internet changed its mind since 2018 https://