kustomize

The "edit this page" links in the right-hand sidebar go to 404 github pages.

I assume this is a hangover of the move to auto-generating these pages from the binary's help output

Steps to reproduce

1. Navigate to any page in the 'Flux CLI' section
2. Click on 'Edit this page' in the right hand side bar

For example, under 'Flux CLI' > 'Flux' 'Edi

We are adding support custom resource ordering in kpt live with the introduction of the depends-on annotation (GoogleContainerTools/kpt#2565). The resource references includes the namespace and name of resources, which means we should make sure they are updated when using the set-namespace and ensure-name-substring functions are used. We should update the functions to

Expected behavior

When running the terraform step, all plan contents should be visible or there should be a scroll bar.

Actual behavior

A scrollbar never appears, and content clips off the bottom of the screen. If the page zoom is changed, content reflows and a scroll bar appears.

Information

• Ship version: 0.43.1
• Command line run: ship init ./ship.yaml
• Chrome v

It would be nice to be able to disable log analytics for an AKS cluster. As far as I can tell, right now it's not customizable via kubestack

Do you plan to provide an image for ARM ? I found the Gatekeeper docker image for ARM (https://hub.docker.com/r/raspbernetes/gatekeeper) but nothing for gatekeeper-policy-manager.
I would try to install it on Raspberry pi :-)

As i'm browsing through the samples folder of Istio (which I've added to Monokle) - i would like to be able to filter resources defined in a specific file or folder - instead of having to browse that folder specifically - or add exclusions for other files.

Suggest to add this to the filter panel:

• "Contained in" File/Folder selector (as we have when creating a resource?) - one value is enou

Now that the framework is in place for ephemeral E2E tests we should add more, with the goal being the eventual elimination of the GitLab-based E2E testing using the e2e.sh shell script.

• Let's start making the GitHub Actions based tests required in PRs through the Branch Protection Rule in the repo settings
• E2E tests should all run in parallel to minimize the time it takes to run them

Figure out what it will take to run kfilt as a kubectl plugin

• docs
• installation instructions
• usage examples
• etc.

This can be split into multiple issues if necessary.