Ae prod#2381
Closed
entlein wants to merge 370 commits into
Closed
Conversation
Signed-off-by: entlein <einentlein@gmail.com>
Signed-off-by: entlein <einentlein@gmail.com>
Signed-off-by: entlein <einentlein@gmail.com>
Signed-off-by: entlein <einentlein@gmail.com>
Signed-off-by: entlein <einentlein@gmail.com>
Signed-off-by: entlein <einentlein@gmail.com>
Adding a brute force helm install for vizier from a public dockerhub
Merge pipeline-support-wip from ddelnano
Pipeline support wip
… for socks proxy in gcloud ssh Signed-off-by: entlein <einentlein@gmail.com>
Signed-off-by: Duck <70207455+entlein@users.noreply.github.com>
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
…ata at once Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
…ling logical_planner_test in place Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
…nges to get partway through a clickhouse pxl script executing. Currently failing at grpc_sink_node exec Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
…carnot_executable Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
…useSourceNode against non Pixie clickhouse data (vector populated) Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
…r/add-clickhouse-source-and-sink-nodes Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
…nfig adaptive export config
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
…parameterize jobs for easy fork usage (pixie-io#2363) Summary: Fix and modernize release workflows, complete ghcr.io migration, and parameterize jobs for easy fork usage Completes the ghcr.io migration started by earlier changes, repairs the bit-rot that accumulated since these workflows last ran, and parameterizes them via `vars.IMAGE_REPO` and `${{ github.repository }}` so forks can publish to their own registry without editing the workflows. Note: This change is best reviewed commit by commit. Relevant Issues: N/A Type of change: /kind cleanup Test Plan: Built vizier, operator, cli and cloud releases for the https://github.com/k8sstormcenter/pixie fork based off these changes * Ran a few pre-release builds that included an earlier version of these changes ([cloud-release](https://github.com/pixie-io/pixie/actions/runs/24548517833)) * Verify macos signing variable is set ``` $ gh variable --repo pixie-io/pixie get ENABLE_MACOS_SIGNING true ``` Changelog Message: Future cloud, operator and vizier release images will now pushed to ghcr.io/pixie-io instead of gcr.io --------- Signed-off-by: Dom Del Nano <ddelnano@gmail.com> GitOrigin-RevId: 44d42f1
…ra-cleanup Graduate release files from copybara ignored_dirs
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
…ins-from-copybara Remove `tools/` and `ci/` from copybara pin
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
…read/export functionality Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
… and soc suite Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Summary: Use correct platform for `container_push` pusher binary I'm not sure why upstream switched this to [target](bazelbuild/rules_docker@e48c7cc), but this fails on our current GitHub runners ([build link](https://github.com/pixie-io/pixie/actions/runs/25715727034/job/75507683014)): ``` Target //k8s/vizier:vizier_images_push up-to-date: bazel-bin/k8s/vizier/vizier_images_push INFO: Elapsed time: 817.792s, Critical Path: 223.45s INFO: 5492 processes: 430 remote cache hit, 48 internal, 5014 processwrapper-sandbox. INFO: Build completed successfully, 5492 total actions INFO: INFO: Running command line: bazel-bin/k8s/vizier/vizier_images_push INFO: Streaming build results to: https://app.buildbuddy.io/invocation/27eff3a9-fc64-4408-8ca4-1c57014fb23d /github/home/.cache/bazel/_bazel_root/56ec069a32c4abebc78228236a835895/execroot/px/bazel-out/k8-opt/bin/k8s/vizier/vizier_images_push.runfiles/px/k8s/vizier/vizier_images_push.0.push: line 31: /github/home/.cache/bazel/_bazel_root/56ec069a32c4abebc78228236a835895/execroot/px/bazel-out/k8-opt/bin/k8s/vizier/vizier_images_push.runfiles/px/../io_bazel_rules_docker/container/go/cmd/pusher/pusher_/pusher: cannot execute binary file: Exec format error ``` Relevant Issues: N/A Type of change: /kind bugfix Test Plan: vizier-release job tested with a similar change. I ccidentally used `cfg = "host"` on the latest build but should have same effect. Signed-off-by: Dom Del Nano <ddelnano@gmail.com> GitOrigin-RevId: ce0f158
… new LTS versions for 6.x kernels. (pixie-io#2350) Summary: Trim linux headers to LTS kernel versions for 4.x and 5.x and include new LTS versions for 6.x kernels. Relevant Issues: pixie-io#2275, pixie-io#2344 Type of change: /kind dependency Test Plan: Deploy a vizier on the following platforms and compared pl7 headers vs the new pl8 - [x] Bottlerocket - [x] Amazon Linux - [x] k0s (6.12 kernel) - [x] Google COS - Verified that the new build process via `make prepare` creates similarly sized tar files and has roughly the same files present (some files were missing like .config, Makefile, Module.symvers, Kconfig, compile.h, but not of these are used by the PEM) <details><summary>Bottlerocket /etc/os-release</summary> ``` I20260410 02:06:57.094861 9891 system_info.cc:35] /host/etc/os-release: NAME=Bottlerocket ID=bottlerocket VERSION="1.57.0 (aws-k8s-1.33)" PRETTY_NAME="Bottlerocket OS 1.57.0 (aws-k8s-1.33)" VARIANT_ID=aws-k8s-1.33 VERSION_ID=1.57.0 BUILD_ID=beaadc52 VENDOR_NAME=Bottlerocket HOME_URL="https://github.com/bottlerocket-os/bottlerocket" SUPPORT_URL="https://github.com/bottlerocket-os/bottlerocket/discussions" BUG_REPORT_URL="https://github.com/bottlerocket-os/bottlerocket/issues" DOCUMENTATION_URL="https://bottlerocket.dev" ``` </details> <details><summary>Google COS /etc/os-release</summary> ``` I20260410 01:17:27.298167 14802 system_info.cc:35] /host/etc/os-release: NAME="Container-Optimized OS" ID=cos PRETTY_NAME="Container-Optimized OS from Google" HOME_URL="https://cloud.google.com/container-optimized-os/docs" BUG_REPORT_URL="https://cloud.google.com/container-optimized-os/docs/resources/support-policy#contact_us" GOOGLE_METRICS_PRODUCT_ID=26 KERNEL_COMMIT_ID=46c2d01887bed5038cc2b8bbd801ae2f7985e7f0 GOOGLE_CRASH_ID=Lakitu VERSION=125 VERSION_ID=125 BUILD_ID=19216.104.126 ``` </details> <details><summary>header size comparision</summary> ``` Size Comparison ┌──────────┬────────┬───────────┬─────────┬─────────┐ │ Version │ Arch │ pl8 opt │ pl8 orig │ pl7 │ ├──────────┼────────┼───────────┼─────────┼─────────┤ │ 4.18.20 │ x86_64 │ 7.6M │ 9.9M │ 7.7M │ ├──────────┼────────┼───────────┼─────────┼─────────┤ │ 4.18.20 │ arm64 │ 7.3M │ 8.1M │ 7.5M │ ├──────────┼────────┼───────────┼─────────┼─────────┤ │ 5.10.252 │ x86_64 │ 8.7M │ 12M │ N/A │ ├──────────┼────────┼───────────┼─────────┼─────────┤ │ 5.10.252 │ arm64 │ 8.4M │ 9.9M │ N/A │ ├──────────┼────────┼───────────┼─────────┼─────────┤ │ 5.14.21 │ x86_64 │ 8.9M │ 12M │ 8.8M │ ├──────────┼────────┼───────────┼─────────┼─────────┤ │ 5.14.21 │ arm64 │ 8.6M │ 11M │ 8.8M │ ├──────────┼────────┼───────────┼─────────┼─────────┤ │ 6.1.167 │ x86_64 │ 9.7M │ 13M │ N/A │ ├──────────┼────────┼───────────┼─────────┼─────────┤ │ 6.1.167 │ arm64 │ 9.4M │ 12M │ N/A │ ├──────────┼────────┼───────────┼─────────┼─────────┤ │ 6.6.132 │ x86_64 │ 11M │ 13M │ N/A │ ├──────────┼────────┼───────────┼─────────┼─────────┤ │ 6.6.132 │ arm64 │ 9.8M │ 13M │ N/A │ ├──────────┼────────┼───────────┼─────────┼─────────┤ │ 6.12.80 │ x86_64 │ 11M │ 14M │ N/A │ ├──────────┼────────┼───────────┼─────────┼─────────┤ │ 6.12.80 │ arm64 │ 11M │ 14M │ N/A │ ├──────────┼────────┼───────────┼─────────┼─────────┤ │ 6.18.21 │ x86_64 │ 12M │ 14M │ N/A │ ├──────────┼────────┼───────────┼─────────┼─────────┤ │ 6.18.21 │ arm64 │ 11M │ 16M │ N/A │ ├──────────┼────────┼───────────┼─────────┼─────────┤ │ 6.19.10 │ x86_64 │ 12M │ 14M │ N/A │ ├──────────┼────────┼───────────┼─────────┼─────────┤ │ 6.19.10 │ arm64 │ 12M │ 16M │ N/A │ └──────────┴────────┴───────────┴─────────┴─────────┘ ``` </details> Changelog Message: Update the vizier-pem's prepackaged linux headers to work with newer AMI / cloud images. This fixes an issue where some platforms which don't have linux header packages (like Google COS) wouldn't show protocol tracing data (pixie-io#2344) --------- Signed-off-by: Dom Del Nano <ddelnano@gmail.com> GitOrigin-RevId: c674687
Signed-off-by: Dom Delnano <ddelnano@gmail.com>
[perf_tool] Add perf_clickhouse GitHub action to test pxl clickhouse read/export
entlein
requested a deployment
to
pr-actions-approval
GitHub Actions
Waiting
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.