meshctl experimental check-impact

Evaluate whether an input snapshot is impacted by a provided issue number.

Synopsis

In rare cases, the Solo Support team might provide you with known issue numbers that could potentially impact your Gloo environment. You can run this command to check the input snapshots from your management server against the known issues to receive guidance on the level of impact.

  meshctl experimental check-impact [flags]

Options 

    -h, --help                                                                                 help for check-impact
      --input-snapshot kubectl -n gloo-mesh port-forward deploy/gloo-mesh-mgmt-server 9091   Path to the JSON file containing the input snapshot. You can get an input snapshot by running kubectl -n gloo-mesh port-forward deploy/gloo-mesh-mgmt-server 9091 and `curl "http://localhost:9091/snapshots/input" > input.json`.
      --issue-number int                                                                     Issue number to check the input snapshot against.

Options inherited from parent commands 

        --kubeconfig string    Path to the kubeconfig file for the cluster.
      --kubecontext string   Kubernetes context for the cluster to run the command in.
  -n, --namespace string     Namespace to run the command in. (default "gloo-mesh")
      --plain                Disable styling for terminal output.
  -v, --verbose              Enable verbose logging.

SEE ALSO