Summary:
now that we're updating vizier so that it can be deployed to any namespace, we should follow helm chart conventions a little better.
in general, namespaces are not created in the helm charts. it can be created using the --create-namespace flag on the helm command or should already exist.

this diff updates the generated template so that it no longer includes the namespace resource. if theyre deploying through helm, helm will handle the namespace for them. if they're deploying through --extract_yamls, we can probably assume that they know how to create their own namespace first.

if deploying through the CLI, we can still create the namespace for them if needed.

Note: This will break new Vizier releases for older CLIs, since the old CLIs will still want the namespace YAML! however, more breaking changes are coming in followup diffs, so it's probably not worth extra changes to make sure this doesn't break old CLIs.

Test Plan: ran `px deploy` with/without existing pl namespace.

Reviewers: vihang, zasgar, nserrino

Reviewed By: vihang

JIRA Issues: PP-2684

Differential Revision: https://phab.corp.pixielabs.ai/D8431

GitOrigin-RevId: b170e1ed0e4a6a85ba7b081c1309a667225dfeed

Test Plan: Jenkins

Reviewers: #stirling, jps

Reviewed By: #stirling, jps

Subscribers: oazizi

Differential Revision: https://phab.corp.pixielabs.ai/D8415

GitOrigin-RevId: 97e9ec09292da60e577fccecc8d51d43ca004c7e

Test Plan: Jenkins

Reviewers: #stirling, oazizi

Reviewed By: #stirling, oazizi

Subscribers: oazizi

Differential Revision: https://phab.corp.pixielabs.ai/D8414

GitOrigin-RevId: d5adb73f9d539633f3b26086fb65cb3acc0b8b4c

Summary: This needs to be on the new TransferData() as well as the old one.

Test Plan: Manual.

Reviewers: #stirling, yzhao

Reviewed By: #stirling, yzhao

Differential Revision: https://phab.corp.pixielabs.ai/D8428

GitOrigin-RevId: 12bf5dc8b2d858f17b969a7d3355538b1fbec3cd

Summary: TSIA. This is more in line with our other protos.

Test Plan: Existing tests.

Reviewers: zasgar, michelle

Reviewed By: michelle

JIRA Issues: PP-2671

Differential Revision: https://phab.corp.pixielabs.ai/D8427

GitOrigin-RevId: 97efd0404f8f0e827e7af9fad7807c6b140dd392

Summary: Adds antlr4 jar installation to chef.

Test Plan: ran chef locally and it worked.

Reviewers: zasgar, nserrino, michelle

Reviewed By: michelle

Subscribers: vihang

JIRA Issues: PP-2658

Differential Revision: https://phab.corp.pixielabs.ai/D8379

GitOrigin-RevId: b75af2621e93c55f9e361f21957449f5b4515d49

Summary:
We are updating Vizier so that it can run in any namespace. the first step to doing so is to update vizier so that it does not rely on any hardcoded "pl"s.
instead, we should use the namespace that we can get from the pod metadata.

Test Plan: created an rc, deployed it. updated vizier running on actual release version. verified all cases continue to work/updates worked.

Reviewers: vihang, zasgar, nserrino

Reviewed By: vihang

JIRA Issues: PP-2683

Differential Revision: https://phab.corp.pixielabs.ai/D8420

GitOrigin-RevId: dc945ad85075052f8322e48fd4d8224332b521af

Summary: TSIA

Test Plan: Existing tests still pass.

Reviewers: zasgar, michelle, nserrino

Reviewed By: michelle

JIRA Issues: PP-2661

Differential Revision: https://phab.corp.pixielabs.ai/D8419

GitOrigin-RevId: 61016b2b9ad2c088e57063bd0dff566445208fdf

Summary: TSIA. This is more in line with our other protos.

Test Plan: Existing tests.

Reviewers: michelle, zasgar

Reviewed By: michelle

JIRA Issues: PP-2671

Differential Revision: https://phab.corp.pixielabs.ai/D8421

GitOrigin-RevId: c1c4d617633108dadff408bbfee4cb2118cdc969

Summary:
These are left over from the old python api process and the old vizier
proto locations.

Test Plan: Existing build and tests.

Reviewers: zasgar, michelle

Reviewed By: michelle

JIRA Issues: PP-2671

Differential Revision: https://phab.corp.pixielabs.ai/D8423

GitOrigin-RevId: 73ab605a2c130f9f3780bfe4d3e07cc113632aad

Summary: Chef is failing because of some clownery by the people at the @sourcegraph/lsif-node repo. Replacing their version with the default microsoft package.

Test Plan: ci/collect_and_upload_lsif.sh works. Tbh not sure how this will affect the lsif output.

Reviewers: vihang, nlanam

Reviewed By: vihang

Differential Revision: https://phab.corp.pixielabs.ai/D8409

GitOrigin-RevId: e7240f73e0b5ed77cc5fb2d87f113733997701b7

Summary:
git tells us about all changed files including ones that were deleted.
When triggering all targets due to a change in a `BUILD.bazel` file, check for
existence of the `BUILD.bazel` file so that we don't try to build and test removed
targets.

Test Plan: Ran the script with some folder renames.

Reviewers: zasgar, oazizi, yzhao

Reviewed By: yzhao

Differential Revision: https://phab.corp.pixielabs.ai/D8424

GitOrigin-RevId: 3183e5b1ab679a3ce134cc7d7261498b4d6dbf35

Summary:
scripts/create_gke_cluster.sh: add optional argument -z for zone.

We are adding an argument "-z" to specifiy the zone for the cluster. This is useful for the stirling perf eval flow because we want to run multiple perf evals in parallel (as a single experiement where we have a baseline and multiple perf experiments to evaluate). For isolation, sandboxing, and reproducibility, we spin-up and tear-down a new cluster for the individual experiments. Zone us-west1-a is oversubscribed by our team. Allowing the stirling perf eval flow to choose a different zone (it will use us-west1-b for now) enables the desired parallelism.

Test Plan: Use case by stirling perf eval.

Reviewers: #stirling, zasgar, vihang, michelle, oazizi

Reviewed By: #stirling, oazizi

Subscribers: oazizi

JIRA Issues: PP-2555

Differential Revision: https://phab.corp.pixielabs.ai/D8422

GitOrigin-RevId: 67b329d88f30ccbc7a99ea9993faff5e6351e0ae

Test Plan: Jenkins

Reviewers: #stirling, oazizi

Reviewed By: #stirling, oazizi

Differential Revision: https://phab.corp.pixielabs.ai/D8404

GitOrigin-RevId: 14ad3daed873724d558e1837e86bca0fb8413a62

Test Plan: Jenkins

Reviewers: #stirling, jps

Reviewed By: #stirling, jps

Differential Revision: https://phab.corp.pixielabs.ai/D8417

GitOrigin-RevId: 84ac27b3bba97fbb2264007ec5438cdea0ae9451

Summary: Allow the Go client API to create deploy keys.

Test Plan: Added an example program and ran tests manually. Will add unit tests to this soon.

Reviewers: vihang, michelle

Reviewed By: vihang

JIRA Issues: PC-865

Differential Revision: https://phab.corp.pixielabs.ai/D8412

GitOrigin-RevId: 9940c00958fdcaf96a9a6e184e461c06ec7679d8

Summary: Tidying up a bit. Simplifying some logic.

Test Plan: Existing tests. Should only affect CONN_TRACE logs, so risk is low.

Reviewers: #stirling, yzhao

Reviewed By: #stirling, yzhao

Subscribers: yzhao

Differential Revision: https://phab.corp.pixielabs.ai/D8351

GitOrigin-RevId: 4509cd87365dfeb63ca2cbc7dc563a338ff3b628

Summary:
Removes all instances of now() in ConnTracker.

Call to now() to be passed in and can be shared across all ConnTrackers.

Test Plan: Existing tests

Reviewers: #stirling, yzhao

Reviewed By: #stirling, yzhao

Subscribers: yzhao

Differential Revision: https://phab.corp.pixielabs.ai/D8349

GitOrigin-RevId: 27eb2c7a789142b16e364ae1a0579ee990bd441d

Test Plan: Jenkins

Reviewers: #stirling, oazizi

Reviewed By: #stirling, oazizi

Differential Revision: https://phab.corp.pixielabs.ai/D8405

GitOrigin-RevId: 246410e5375b5eb867e39e0f2a27d99cd18969fb

Summary: Dependent on D8387. Add interval macro.

Test Plan: Manual Test.

Reviewers: nserrino, vihang

Reviewed By: vihang

JIRA Issues: PC-861

Differential Revision: https://phab.corp.pixielabs.ai/D8398

GitOrigin-RevId: 7bd6b18e6168e51f7f7e28c4e8f38ddc77fdb7ce

Summary: perf_profile_connector.h|cc: converting the symbol cache to a symbolizer with symbolization policy.

Test Plan: Existing tests.

Reviewers: #stirling, oazizi

Reviewed By: #stirling, oazizi

Subscribers: yzhao, oazizi

JIRA Issues: PP-2555, PP-2621

Differential Revision: https://phab.corp.pixielabs.ai/D8393

GitOrigin-RevId: c0c9f31bae12d1efe67ba669924b8b120bce9e09

Summary:
Added support for time macros $__timeFrom() and $__timeTo() in PxL scripts in Grafana.
Users can put these into their Pxl scripts and select/change time ranges via Grafana UI and see
the results in the panel without much zooming in or out. Users don't have to rely on hard-coding times
or putting relative times like "-5m".

Test Plan: Manual tested & Unit Tested.

Reviewers: nserrino, vihang

Reviewed By: vihang

JIRA Issues: PC-851

Differential Revision: https://phab.corp.pixielabs.ai/D8387

GitOrigin-RevId: 019ca542b967a179316c7f593e13262a1d52de31

Summary: Now that all the viziers and cloud use `px` we can safely revert this.

Test Plan: Test on staging.

Reviewers: zasgar, michelle

Reviewed By: michelle

JIRA Issues: PP-2636

Differential Revision: https://phab.corp.pixielabs.ai/D8401

GitOrigin-RevId: 878a37e4ce6130ed13de7999900292dc2ad51483

Summary:
Followup to D8400, loading the go repos before rules_go causes issues with gogo.
Instead of making a large change in our load order and finding other bugs, let's
just patch rules_docker until they fully fix the underlying issue and release
a new version.

Revert "Explicitly depend on google/go-containerregistry to workaround a rules_docker bug"
This reverts commit 4d6cd510abacb8afcb690137f5c358fd90b8ee29.

Test Plan: `bazel build //...`

Reviewers: zasgar, michelle, #third_party_approvers

Reviewed By: zasgar, #third_party_approvers

Differential Revision: https://phab.corp.pixielabs.ai/D8403

GitOrigin-RevId: 26c90c457b35a6671bd29056e5ead33bd87aa767

Summary: OAuthProvider now provides the button componets to AuthBox to enable login/signup instead of the login/sign up pages having them setup.

Test Plan: Tested on skaffold

Reviewers: nlanam, michelle

Reviewed By: nlanam

JIRA Issues: PC-853

Differential Revision: https://phab.corp.pixielabs.ai/D8378

GitOrigin-RevId: a86067bb517404abfa93b7313562cc535223d387

Summary:
the previous diff just set up the boilerplate for the CRD, but didn't actually fill in what fields we want our CRD to contain.
for determining where things should go/what fields we should have, I consulted Pods and NATSCluster CRD.

The vizierSpec mainly contains fields that we allow users to currently configure through the CLI/helm.
The vizierStatus contains fields with information about the vizier's state. for this I mostly copied pods: there is a VizierPhase and optional message that can provide context about why that Vizier is in that state.

Test Plan: everything still builds.

Reviewers: zasgar, vihang

Reviewed By: vihang

Differential Revision: https://phab.corp.pixielabs.ai/D8389

GitOrigin-RevId: 69c475ebe9d3e409c58249f4b89b46ac06ee1836

Test Plan: Jenkins

Reviewers: #stirling, oazizi

Reviewed By: #stirling, oazizi

Differential Revision: https://phab.corp.pixielabs.ai/D8392

GitOrigin-RevId: 2f36d873b225543862a1586097a449789c08a8b5

Summary: We used some messy utils.ts stuff that was leftover from an old version of auth. Updating to follow @nlanam's memo standard.

Test Plan: yarn dev, works

Reviewers: nlanam, michelle

Reviewed By: michelle

Subscribers: nlanam

Differential Revision: https://phab.corp.pixielabs.ai/D8382

GitOrigin-RevId: f5d0c89bea887041818480b6850b8b8a859c6cd0

PC-853: Replace the "variant" prop of AuthBox and move the variant things to props, and replace Login Button with composition

Summary: Variant stuff in authbox was really annoying and felt dirty. This cleans it up and also makes the code ready for any number of login flows by pushing that to the children.

Test Plan: Tested with yarn dev to make sure stuff doesn't break.

Reviewers: nlanam, michelle

Reviewed By: nlanam

JIRA Issues: PC-853

Differential Revision: https://phab.corp.pixielabs.ai/D8366

GitOrigin-RevId: d5e8be99c61d535e55316a8f20fe10e80c06bc3c

Summary: TSIA

Test Plan: Future push to prod demos will test this.

Reviewers: zasgar, nserrino

Reviewed By: zasgar

Differential Revision: https://phab.corp.pixielabs.ai/D8399

GitOrigin-RevId: 108f37d72dc5284850e452b97234d4a78dff2440

Summary:
This is to work around https://github.com/bazelbuild/rules_docker/issues/1814
For more context, also see https://github.com/bazelbuild/rules_docker/pull/1815
and https://github.com/google/go-containerregistry/issues/997

Test Plan: Jenkins build should run now.

Reviewers: zasgar, #third_party_approvers

Reviewed By: zasgar, #third_party_approvers

Differential Revision: https://phab.corp.pixielabs.ai/D8400

GitOrigin-RevId: 4d6cd510abacb8afcb690137f5c358fd90b8ee29

Summary:
Makes the expanded row only as wide as its parent scrolling context, so its own scrollbars are visible. Makes the expanded row follow the viewport rather than the content for horizontal scrolling of the table, making its horizontal position sticky.
To do this in a performant way, a `useScrollPosition` hook is introduced that throttles scroll event handlers to update once per frame rather than thousands of times per second.

Test Plan: Grab this branch, `yarn build_deps && yarn dev`, try running `px/http_data` in the UI. Expand a row in the resulting table. Notice that the row's scrollbar(s) is/are visible even if the whole table is wider. Scroll the table horizontally and watch the expanded row follow along, staying in the same place relative to your viewport.

Reviewers: michelle, vihang

Reviewed By: vihang

Differential Revision: https://phab.corp.pixielabs.ai/D8394

GitOrigin-RevId: 22639277cf49bff9d2ef8777e9fec25bb9864deb

Summary:
deploying the operator through skaffold will speed up the development process.
this diff just adds the skaffold file.

Test Plan: ran `skaffold run -f skaffold/skaffold_operator.yaml`, verified that the operator starts up and runs.

Reviewers: vihang, zasgar

Reviewed By: vihang

JIRA Issues: PP-2653

Differential Revision: https://phab.corp.pixielabs.ai/D8391

GitOrigin-RevId: 619dbb71ad282a696816f2d51f275d294f1c0f10

Summary: TSIA

Test Plan: n/a

Reviewers: vihang

Reviewed By: vihang

Differential Revision: https://phab.corp.pixielabs.ai/D8390

GitOrigin-RevId: 18c636633d10201452a29e91fb69bbd230d4f782

perf_profile_connector.h|cc: prep. work to filter out non-k8s processes from symbolization in the perf. profiler. Make md::UPID a member of SymbolicStackTrace, pass ctx into AggregateStackTraces()

Summary: perf_profile_connector.h|cc: prep. work to filter out non-k8s processes from symbolization in the perf. profiler. Make md::UPID a member of SymbolicStackTrace, pass ctx into AggregateStackTraces()

Test Plan: Existing tests.

Reviewers: #stirling, oazizi

Reviewed By: #stirling, oazizi

JIRA Issues: PP-2555, PP-2621

Differential Revision: https://phab.corp.pixielabs.ai/D8384

GitOrigin-RevId: 2d0f9bdb536203d098041b6d86eaa098842c8f05

Summary:
`/admin` now redirects to `/admin/cluster` (`/admin/cluster/somename` still works). There is also a `/admin/deployment-keys` and `/admin/api-keys`. The tab headers correspond to these new links.
This also gets rid of needless nesting of `<Router>` and cleans up lint/type warnings in touched files. Scouts' rule, and all that.

Test Plan: Try directly browsing to `/admin`, `/admin/api-keys`, and going to the admin page from the Live view (which goes to `/admin`). The API Keys link should directly open that tab; clicking a different tab should update the URL accordingly.

Reviewers: michelle, vihang

Reviewed By: michelle

JIRA Issues: PC-546, PC-674

Differential Revision: https://phab.corp.pixielabs.ai/D8372

GitOrigin-RevId: d95a967ccdc87c47d7d49b0c483368bf613a8c0e

Summary: TSIA

Test Plan: jenkins

Reviewers: vihang

Reviewed By: vihang

Differential Revision: https://phab.corp.pixielabs.ai/D8386

GitOrigin-RevId: b6d92a3a83156052baec2f3f1f7de307eb90eb78

Summary:
a typical operator deployment has:
- the operator deployment to launch the operator pod
- the service account associated with the operator
- clusterroles/clusterrolebindings that allow the operator to modify resources in the cluster.

the clusterroles I included here are the same clusterrules we require for our updaterjob + our new Vizier CRD.

Test Plan: deployed the operator with these YAMLs

Reviewers: vihang, zasgar

Reviewed By: vihang

JIRA Issues: PP-2651

Differential Revision: https://phab.corp.pixielabs.ai/D8368

GitOrigin-RevId: 9288579fb6d267de35e35d50b4699d6b1f48b1ea

Summary:
Adding initial boilerplate for our Vizier operator, based off of the generated kubebuilder project.
kubebuilder generated:
- contents of operator directory
- k8s/operator/crd
I heavily modified the contents of the operator directory to remove the additional items we didnt need and made it work with our build system. removed most of the items in the Makefile except for the commands that help generate the k8s crd yaml and generated go files.

Test Plan: deployed the crd, deployed the operator, and deployed an instance of the Vizier custom resource. verified that the operator detected the change and triggered the "Reconcile" function.

Reviewers: zasgar, vihang, #third_party_approvers

Reviewed By: vihang, #third_party_approvers

JIRA Issues: PP-2650

Differential Revision: https://phab.corp.pixielabs.ai/D8367

GitOrigin-RevId: 2c0ae0e45c97309258f083eea5d33acb2fc15578

Summary: Allow bazel_ci script to work even if experimental directory is missing.

Test Plan: jenkins

Reviewers: vihang

Reviewed By: vihang

JIRA Issues: PP-2612

Differential Revision: https://phab.corp.pixielabs.ai/D8385

GitOrigin-RevId: 20fa1fd2debe44d15c7d9274e020133ce1e778ca