Closed bartsmykla closed 2 months ago
Name | Link |
---|---|
Latest commit | bef4978c71ea5c35f84b550a5f885d277ecd2858 |
Latest deploy log | https://app.netlify.com/sites/kuma/deploys/661fa86d23bc590008816a58 |
Deploy Preview | https://deploy-preview-1738--kuma.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
Lighthouse |
1 paths audited Performance: 95 (π’ up 43 from production) Accessibility: 90 (no change from production) Best Practices: 100 (no change from production) SEO: 85 (no change from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports |
To edit notification comments on pull requests, go to your Netlify site configuration.
Rendered, changed page: https://deploy-preview-1738--kuma.netlify.app/docs/2.7.x/using-mesh/managing-ingress-traffic/gateway-api/
Closes https://github.com/kumahq/kuma-website/issues/1719
apiVersion
of GAPI resources tov1
Gateway API is GA now and we can change the version of resources fromv1beta1
tov1
kubectl get ...
commands to separate blocks Now you can copy commands when want to follow instructions to the letter easier.{% capture gateway %}
By using{% capture ... %}
we can make sure rendered content will be correctly indented, but so far we unnecessarily put too much content there, so it caused confusion. ChangedMeshGatewayRoute
s in How it works for>= 2.7.0
From 2.7.0 we are internally not generatingMeshGatewayRoute
s, so there is no need of mentioning it.<= 2.6.x
Kuma
in the warning we should use{{site.mesh_product_name}}
if_version
blocks.yaml
To be consistent with the rest of the page and to make it easier for people which want to copy the resource to file I changed some of the code blocks fromsh
with instructionsecho "..." | kubectl apply -f-
to be justyaml
s with pure manifests.Did you sign your commit? Instructions: π
Have you read Contributing guidelines?: π