10.244.0.192:9080                                HEALTHY                  outbound|9080||reviews.default.svc.cluster.local
10.244.0.193:9080                                HEALTHY                  outbound|9080||reviews.default.svc.cluster.local
10.244.0.195:9080                                HEALTHY                  outbound|9080||reviews.default.svc.cluster.local
./var/run/secrets/workload-spiffe-uds/socket     HEALTHY                  sds-grpc

                                        "name": "inbound-vip|9080||reviews.default.svc.cluster.local-http",
                                        "typed_config": {
                                          "@type": "type.googleapis.com/google.protobuf.StringValue",
                                          "value": "inbound-vip|9080||reviews.default.svc.cluster.local-http"
                                        }

### Create a Pull Request

Pull requests can be created via GitHub. Refer to [this document](https://help.github.com/articles/creating-a-pull-request/) for detailed steps on how to create a pull request. After a Pull Request gets peer reviewed and approved, it will be merged.

## FAQs

### How does ``MinIO`` manage dependencies?

``MinIO`` uses `go mod` to manage its dependencies.

# update CODE and DATA below, and then run
#
#	./update.bash -commit
#
# That will prepare the files and create the commit.
#
# To review such a commit (as the reviewer), use:
#
#	git codereview change NNNNNN   # CL number
#	cd lib/time
#	./update.bash
#
# If it prints "No updates needed.", then the generated files
# in the CL match the update.bash in the CL.

                                    "tlsMode": "istio"
                                },
                                "istio": {
                                    "workload": "reviews-v3;default;reviews;v3;Kubernetes"
                                }
                            }
                        },
                        "loadBalancingWeight": 1
                    },
                    {

* To avoid asking the same thing multiple times during code review.
* To explain *rejected solutions*, for now and future development, in case they are proposed again.

ADRs can be written by any team.
Like code, they should be reviewed by any other relevant teams.
The goal is not to *own* a decision, but to *share* it with other teams, and improve the build tool together.

### Format

The format for ADR should follow this template:

```markdown

* To avoid asking the same thing multiple times during code review.
* To explain *rejected solutions*, for now, and future development, in case they are proposed again.

ADRs can be written by any team.
Like code, they should be reviewed by any other relevant teams.
The goal is not to *own* a decision, but to *share* it with other teams, and improve the build tool together.

### Format

The format for ADR should follow this template:

```markdown

                                                },
                                                "istio": {
                                                    "workload": "reviews-v3;default;reviews;v3;Kubernetes"
                                                }
                                            }
                                        },

# That tree can be copied to a machine of the given target type
# and used as $GOROOT_BOOTSTRAP to bootstrap a local build.
#
# Only changes that have been committed to Git (at least locally,
# not necessary reviewed and submitted to master) are included in the tree.
#
# See also golang.org/x/build/cmd/genbootstrap, which is used
# to generate bootstrap tgz files for builders.

set -e

if [ "$GOOS" = "" -o "$GOARCH" = "" ]; then

          <option name="linkRegexp" value="https://jetbrains.team/p/$1/reviews/$3" />
        </IssueNavigationLink>
        <IssueNavigationLink>
          <option name="issueRegexp" value="KOTLIN-(MR|CR)-(\d+)" />
          <option name="linkRegexp" value="https://kotlin.jetbrains.space/p/kotlin/reviews/$2" />
        </IssueNavigationLink>
      </list>
    </option>
  </component>