Skip to content

Instantly share code, notes, and snippets.

View resouer's full-sized avatar
🏡
Mountain View

Lei Zhang (Harry) resouer

🏡
Mountain View
  • NVIDIA
  • Bay Area
  • 20:29 (UTC -08:00)
View GitHub Profile
{
"updated": "2026-11-15T23:04:09.794598+00:00",
"readhub": [
{
"title": "SpaceX 首次用发射塔机械臂成功捕获返回的星舰飞船",
"summary": "SpaceX 在星舰第 15 次试飞任务中,首次成功利用发射塔「筷子」机械臂捕获从地球轨道返回的星舰上面级飞船,成为历史上首家将轨道级火箭上面级送回发射场并通过发射塔完成捕获的公司。此次任务中,Ship 42 搭乘助推器 B22 升空入轨后顺利完成任务,因飞船隔热罩状态良好,地面控制人员放弃备用海上溅落方案。星舰飞船完成约 14 圈轨道飞行后脱离轨道、重入大气层,最终被成功捕获。不过此次任务未完全",
"link": "https://readhub.cn/topic/8y3xl5nHsub"
},
{
"title": "BLG 夺 S16 全球总决赛冠军 B 站免费送大会员",
@resouer
resouer / app.yaml
Last active June 8, 2021 05:24
A sample Open Application Model (OAM) deployment plan
apiVersion: core.oam.dev/v1
kind: Application
metadata:
name: awesome-blog
spec:
components:
- name: web
type: helm-chart
properties:
image: bitnami/wordpress
@resouer
resouer / platform.md
Last active November 30, 2020 22:56
My dream platform

My dream platform:

  1. Single binary install on nodes, and easy to join them into a cluster.

  2. Resources defined as JSON with comments in a simple format with JSON Schema URLs denoting resource types - I should be able to run 1 container with 3 lines of resource definition.

  3. Everything as a CRD... No resources or funcionality pre-installed and instead available via publicly hosted HTTPS schema URLs.

  4. Pluggable / auto-installed runtimes based on the schema URL or a "runtime" field: containers, vms, firecracker, wasm, maybe even bare processes, etc.

@resouer
resouer / vela.yaml
Last active November 11, 2020 23:56
name: _my-app-name_
services:
_my-service-name_:
build:
docker:
file: _Dockerfile_name_
context: _Dockerfile_path_
myapp: {
components: {
frontend: {
containerized:{
image: "nginx:v1"
port: "8080"
}
traits: {
route: {
domain: "www.example.com"
```console
$ rudr --help
✈️ A Micro App Plafrom for Kubernetes.
Commands
Getting Started 🌱
env Set your enviroment (e.g. dev,stage,prod).
docs Open the rudr docs.
---
apiVersion: core.oam.dev/v1alpha1
kind: WorkloadDefinition
metadata:
name: service.serving.knative.dev
spec:
definitionRef:
# reference to the name of real-world crd
name: service.serving.knative.dev
---
# -------------------------- Step 1: Define and install WorkloadType and Trait ---------------------
---
apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
name: radius.cache.crossplane.io
annotations:
core.oam.dev/oam-type: WorkloadType
scope: Namespaced
names:
# Step 1: Define and install WorkloadType and Trait
---
apiVersion: core.oam.dev/v1alpha1
kind: WorkloadType
metadata:
name: cache.crossplane.io/v1.Radius # we endorse G/V/K convension as WorkloadType name
spec:
schematic: |
apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
apiVersion: core.oam.dev/v1alpha1
kind: ApplicationConfiguration
metadata:
name: first-app
spec:
components:
- componentName: helloworld-python-v1
instanceName: first-app-helloworld-python-v1
parameterValues:
- name: target