- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 176 for describe (0.18 sec)
-
istioctl/pkg/describe/describe.go
cmd := &cobra.Command{ Use: "pod <pod>", Aliases: []string{"po"}, Short: "Describe pods and their Istio configuration [kube-only]", Long: `Analyzes pod, its Services, DestinationRules, and VirtualServices and reports the configuration objects that affect that pod.`, Example: ` istioctl experimental describe pod productpage-v1-c7765c886-7zzd4`, RunE: func(cmd *cobra.Command, args []string) error {
Go - Registered: Wed Mar 27 22:53:09 GMT 2024 - Last Modified: Tue Mar 12 18:49:10 GMT 2024 - 46.2K bytes - Viewed (0) -
istioctl/pkg/describe/describe_test.go
func TestDescribe(t *testing.T) { productPageConfigPath := "testdata/describe/http_config.json" config, err := os.ReadFile(productPageConfigPath) if err != nil { t.Fatalf("failed to read %s: %v", productPageConfigPath, err) } cases := []execAndK8sConfigTestCase{ { // case 0 args: []string{}, expectedString: "Describe resource and related Istio configuration", }, { // case 2 no pod
Go - Registered: Wed Mar 27 22:53:09 GMT 2024 - Last Modified: Fri Mar 15 08:28:50 GMT 2024 - 22.5K bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/feature_request.md
name: Feature request about: Suggest an idea to improve Istio --- (This is used to request new product features, please visit <https://github.com/istio/istio/discussions> for questions on using Istio) **Describe the feature request** **Describe alternatives you've considered** **Affected product area (please put an X in all that apply)** [ ] Ambient [ ] Docs [ ] Dual Stack [ ] Installation [ ] Networking
Plain Text - Registered: Wed Mar 27 22:53:09 GMT 2024 - Last Modified: Mon Feb 12 19:42:48 GMT 2024 - 707 bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/11-language-change.yml
description: If so, how does this proposal differ? placeholder: | Yes or No If yes, 1. Mention the related proposals 2. then describe how this proposal differs validations: required: true - type: textarea id: error-handling-proposal attributes: label: Does this affect error handling?
Others - Registered: Tue Mar 26 11:13:08 GMT 2024 - Last Modified: Wed Nov 22 20:49:24 GMT 2023 - 4.7K bytes - Viewed (0) -
docker-buildx.sh
#!/bin/bash sudo sysctl net.ipv6.conf.all.disable_ipv6=0 release=$(git describe --abbrev=0 --tags) docker buildx build --push --no-cache \ --build-arg RELEASE="${release}" \ -t "minio/minio:latest" \ -t "quay.io/minio/minio:latest" \ -t "minio/minio:${release}" \ -t "quay.io/minio/minio:${release}" \ --platform=linux/arm64,linux/amd64,linux/ppc64le,linux/s390x \ -f Dockerfile.release . docker buildx prune -f
Shell Script - Registered: Sun Mar 24 19:28:08 GMT 2024 - Last Modified: Wed Nov 01 18:37:25 GMT 2023 - 983 bytes - Viewed (0) -
architecture/standards/0002-avoid-using-java-serialization.md
Java serialization does not enforce type safety as strictly as some alternatives, potentially leading to runtime errors. ## Decision We do not use Java serialization. Instead, we use custom serialization where we explicitly describe how data objects should be serialized and deserialized. For internal purposes, we use binary formats for their brevity. We use the `Serializer` abstraction to separate the actual implementation of serialization from its uses.
Plain Text - Registered: Wed Mar 27 11:36:08 GMT 2024 - Last Modified: Thu Feb 29 22:32:18 GMT 2024 - 2.3K bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/40_contributor_documentation.yml
- Typo (please open a PR instead) validations: required: true - type: textarea id: description attributes: label: Problem description description: | Please describe the problem as concisely as possible. validations: required: true - type: textarea id: context attributes: label: Context (optional) description: |
Others - Registered: Wed Mar 27 11:36:08 GMT 2024 - Last Modified: Mon Jan 15 10:01:01 GMT 2024 - 1.6K bytes - Viewed (0) -
architecture-standards/0002-avoid-using-java-serialization.md
## Decision We do not use Java serialization. Instead, we use custom serialization where we explicitly describe how data objects should be serialized and deserialized. For internal purposes, we use binary formats for their brevity. We use the `Serializer` abstraction to separate the actual implementation of serialization from its uses.
Plain Text - Registered: Wed Feb 14 11:36:15 GMT 2024 - Last Modified: Thu Feb 08 21:48:27 GMT 2024 - 1.9K bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/bug_report.yaml
Thank you for filing a bug report. Please help us identify and resolve the bug by filling out the following fields. - type: textarea attributes: label: Description description: Please describe the issue you encountered. validations: required: true - type: textarea attributes: label: Example description: >
Others - Registered: Fri Mar 22 12:43:11 GMT 2024 - Last Modified: Fri Oct 27 19:53:41 GMT 2023 - 2.2K bytes - Viewed (0) -
architecture-standards/0001-use-architectural-decision-records.md
## Decision The *Build Tool Team* has decided to use Architectural Decision Records (aka ADR) to track decisions we want to follow. The main logic with ADRs is to describe (architectural) decisions made: * To provide best practices and solutions we (as *build tool* team) want to promote. * To avoid asking the same thing multiple times during code review.
Plain Text - Registered: Wed Feb 14 11:36:15 GMT 2024 - Last Modified: Wed Feb 07 00:43:19 GMT 2024 - 2.8K bytes - Viewed (0)