Skip to main content

acshame

acshame
acshame

  1. ## EKS Upgarde Progress

    | Environment | Region | Cluster Versions |
    | ----------- | ------- | ------------------------------------------------------------ |
    | Dev | Beijing | Service: v1.33, ArgoCD: v1.33, Testkube: v1.32 |
    | Dev | Ningxia | Service: v1.33 |
    | QA | Beijing | Service: v1.31 (暂未继续升级，若需可供后续创建multi-cluster测试集群使用) |
    | QA | Ningxia | Service: v1.33 |
    | Prod | Beijing | Service: v1.30, ArgoCD: v1.33, Testkube: v1.32 |
    | Prod | Ningxia | Service: v1.30 |



    ## EKS Multi-Cluster

    ### requirements

    1. Ensure no interruption to the DKMS service during EKS upgrades and new version releases.
    2. Support blue/green deployments and canary (gradual) releases.



    | Solutions | Description | Pros | Cons | AWS Recommendation |
    | --------- | ----------- | ---- | ---- | ------------------ |

    | Route53 Switch | Two NLBs (NLB → ALB → EKS), use Route53 Weighted Routing to roughly switch traffic | 1. Easy to implement; 2. clear separation | 1. DNS TTL (60s) delay; 2. SDK client DNS caching may cause failover traffic to Ningxia | ✅ AWS Recommended |
    | ------------------ | ------------------------------------------------------------ | ----------------------------------------- | ------------------------------------------------------------ | ----------------- |

    | Shared NLB | Two ALBs connected as Target Groups of same NLB; switch by binding/unbinding target groups | 1. No Route53 ops; 2. faster traffic shift | 1. Client reconnect; | ✅ Recommended |
    | -------------- | ------------------------------------------------------------ | ------------------------------------------ | --------------------- | ------------- |

    | Shared ALB | One ALB forwards to 2 EKS clusters via modify TargetGroupBinding | 1. Support blue/green deployments and canary (gradual) releases. | 1. High ops complexity; 2. risk of ALB/Ingress re-creation | ❌ Not recommended |
    | -------------- | ------------------------------------------------------------ | ------------------------------------------------------------ | ---------------------------------------------------------- | ----------------- |
    | | | | | |



    ### Option 1: Route53 Switch

    #### AS-IS (Before Active-Active)

    graph TD
  A[Clients] --> B[Route53 - Simple]
  B --> C[NLB - Beijing]
  C --> D[ALB - Beijing]
  D --> E[EKS Cluster - v1]


    #### TO-BE (Blue/Green with Route53 Weighted Routing)

    graph TD
  A[Clients] --> B[Route53 - Weighted TTL 60s]
  B --> C1[NLB - Beijing] --> D1[ALB - Blue] --> E1[EKS - v1]
  B --> C2[NLB - Beijing] --> D2[ALB - Green] --> E2[EKS - v2]


    ------

    ### Option 2: Shared NLB with Two ALBs

    #### AS-IS

    graph TD
  A[Clients] --> B[Route53 - Simple]
  B --> C[NLB]
  C --> D[ALB - v1] --> E[EKS Cluster - v1]


    #### TO-BE (Switch Target Groups)

    graph TD
  A[Clients] --> B[Route53 - Simple]
  B --> C[NLB]
  C --> D1[ALB - Blue] --> E1[EKS - v1]
  C --> D2[ALB - Green] --> E2[EKS - v2]


    > 🔁 During upgrade: Unbind D1, bind D2

    ------

    ### Option 3: Shared ALB Across Clusters

    #### AS-IS

    graph TD
  A[Clients] --> B[Route53 - Simple]
  B --> C[NLB] --> D[ALB] --> E[EKS Cluster - v1]


    #### TO-BE (Switch TargetGroupBinding)

    graph TD
  A[Clients] --> B[Route53 - Simple]
  B --> C[NLB] --> D[ALB]
  D --> E1[EKS - v1]
  D --> E2[EKS - v2]


    > ⚠️ Risk: ALB/Ingress may be recreated when changing bindings

  2. Hi all,



    Thanks for your time last week. With an active-active cluster requirement confirmed, we summarized the key notes:

    Two solutions discussed,
    Replicate NLB ---> ALB ---> EKS Cluster flow: Easier migration approach from current single EKS cluster to active-active setup, but for blue/green deployments, DNS records may cache on the client side:
    Set Route53 DNS TTL to 60 seconds
    Implement gradual traffic shift: reduce traffic to blue environment before updates, monitor NLB connection draining, then complete the cutover
    Consider client-side connection refresh mechanisms if traffic routing doesn't behave as expected due to persistent connections
    · TargetGroupBinding Approach: 1/ high risk to make current ALBs detach from aws-load-balancer-controller management: potential ALB recreating(ingress recreating), cache management of ALB, etc. 2/how to remove the ingress object safely, may not be deleted gracefully. (edited)

    2. Active-active EKS clusters tips and some recommendations,

    Be Stateless from application or EKS perspective: don't store session data locally, no configuration in the local files, etc.
    No circular traffic patterns between EKS clusters
    Kube-burner is for EKS control plane scaling test.
    Recommend validating the DR in Ningxia region work as expected.
    Recommend build an Observation platform for easier monitoring, tracking


    Plus, Key Considerations for EKS cluster's upgrade with Blue/Green,

    Network Planning and Resource Isolation
    Pay careful attention to the network planning for both new and existing clusters. Since both EKS clusters will be deployed within the same VPC, it is critical to strictly differentiate the subnet configurations, security group settings, and corresponding resource tags between the clusters to prevent accidental deletion of any resources.

    ALB Metrics and Health Check Configuration
    Monitor ALB metrics closely and configure proper health checks for critical services. If ALB connection counts accurately reflect business traffic patterns, prioritize monitoring these metrics as key performance indicators.

    Route 53 Weighted Routing TTL Configuration
    When implementing traffic management through Route 53 weighted routing, ensure that the TTL is set to no more than 60 seconds to enable rapid traffic switching capabilities.

    Testing Environment Validation
    It is strongly recommended to conduct comprehensive testing of the entire setup in a testing environment before implementing in production.

  3. 2023-10-24患者胸部放疗结束8月，未诉明显不适，患者体重 恢复至患病前68公斤。瘤标：NSE 16.2ng/ml。胸CT：食管癌 疗后改变、大致同前。多发转移淋巴结同前。2023/10/24颈淋 巴结CT增强：扫及食管上段管壁增厚大致同前，建议结合专科 检查。 左侧锁骨上多发肿大淋巴结同前， 转移？ 颈部多发小淋巴 结同前，良性可能，建议随访。2023/10/20食道钡餐造影:食管 胸中段癌疗后改变。腹CT未见明显异常 2023-11-7 放疗结束8月余。饮食基本正常，间断声音嘶哑1-2天 后可缓解。开尼妥珠单抗自备2周期。 2024-02-04 患者放疗结束1年，目前应用尼妥珠单抗治疗中， 复查看结果，胸腹部CT及颈部CT未见转移。 2024-02-27患者家属代诊开尼妥珠单抗。 2024-5-23 患者放疗结束1年3月，患者无特殊不适，复查颈胸 腹部增强CT、食管造影提示病情稳定，未见明确复发转移。 2024-06-04 患者目前尼妥珠单抗靶向治疗中，偶有咳嗽，无其 他不适，继续开药。 2024-08-29放疗后1年半，咳嗽伴咳痰目前可进普食，体重 无明显下降。全面复查未见明显进展。 2024-09-10 放疗后1年半，患者胃镜检查C13 （-）_，胃镜：食 管瘢痕形成， 符合治疗后改变；2.慢性萎缩性胃炎,C2； 病理： (食管瘢痕）活检：－表浅鳞状上皮粘膜轻度慢性炎,伴轻度活 动性炎 2024-09-26 放疗后1年半，预2024-10-10输靶向药物。 2024-11-26 放疗结束近2年，复查。目前可进软食，体重无明显 下降。全面复查未见肿瘤进展。 2024-12-10开单，预约尼妥珠单抗。 2025-3-7 患者复查颈部赊胸部、腹部CT及食道钡餐未见肿瘤 进展，体重下降，进食正常。 2025-3-27 开单 2025-7-8 就诊，放疗结束2年半，目前咳嗽1月，体重下降 2kg,2025-07-04胸CT:食管中下段管壁不均匀异常增厚同 前。双侧锁骨上、纵隔、《右肺门及胃小弯侧多发淋巴结同前追 查。左肺新发多发结节， 考虑转移。双肺纵隔旁斑片灶同前， 考 虑放疗后改变。2025/6/30 细胞角蛋白19片段 3.78ng/ml，★ 癌胚抗原 18.42ng/ml，神经元特异性烯醇化酶 19.3ng/ml

  4. 2022-11-2开始行白蛋白紫杉醇+铂类药+卡瑞利珠*2治疗 2022-12-22行第3周期白蛋白紫杉醇+顺铂+信迪利单抗治疗。 2022-12-22评效，我院胸外科就诊考虑肿瘤与主动脉关系密切 不建议手术。咨询放射治疗。 目前患者乏力明显，恶心、呕吐。 2023-01-10 患者今日开始放疗，具体：GTV，食管原发灶+右锁 骨上、4区、8区转移淋巴结，59.4Gy/33次；CTV，GTV四周扩 8mm，食管病灶上下扩3cm，包括双侧锁骨上、1、2、47、 8区淋巴引流区，解剖结构修回，59.4Gy/33次；95%PTV， CTV 三维外扩5mm，59.4Gy/33次。 2023-01-12行第1周期化疗联合靶向治疗，具体：白蛋白紫杉醇 175mg/m2 300mg d1,顺铂75mg/m2 70mg d1,60mg d2, q21d，尼妥珠单抗400mgqw。 2023-01-19.患者今日放疗第8次，行第2次尼妥珠单抗治疗，应 用长效升白针预放升白治疗。 诉剑突下轻度疼痛感， 食欲减退。 复查血常规提示白细胞减低1度， 中性粒细胞正常，血小板减低2 度。 2023-2-2患者今日放疗第17次，放射性食管炎1度。今日复查血 常规肝肾功未见明显异常， 2023-2-7 患者今日放疗第20次，放射性食管炎1度。预约改野 CT定位。 2023-2-16 患者今日放疗第27次，放射性食管炎1度。拟于02- 20执行改野计划。复查血常规未见异常，肝肾功提示转氨酶升 高1度。 20230223 患者今日放疗32次，患者皮肤反应I度，食道炎I度 吞咽困难I度，体重稳定，无其他明显不适。WBC 3.63； 2023-03-28 患者放疗结束1月，间断咳嗽咳痰， 饮食已恢复普 食，体重增加1-2Kg。复查腹部CT未见转移征象，胸部CT、颈 部CT报告未归。拟于明日行食道钡餐造影。血常规、生化瘤肿 标基本正常。 2023-4-14 患者目前仍间断咳嗽，未诉其他明显不适，进食可。 预约04-28、05-05尼妥珠单抗。 2023-7-6患者胸部放疗结束4个月复查，咳嗽较前好转，轻度 咳嗽咳痰，无其他明显不适。本次复查基本同前，血常规提示白 细胞减低1度。肿标NSE轻度升高。已完成12次泰欣生治疗。继 续靶向治疗； 2023-7-27 患者胸部放疗结束5月，未诉明显不适。预约靶向治 疗

  5. 检查所见:
    对比2025-02-21食管钡餐造影：食管胸中段局限管腔轻度扩张受限同前，管壁略显僵硬，管腔轻度狭窄同前，
    长约30mm，口服钡剂下行未见受阻征象。贲门形态及开放良好。

  6. 检查所见：
    与2025-02-18颈部CT对比：左侧锁骨上区多发淋巴结同前，较大约
    22x7mm （IM62）。双侧颈深、颈浅多发淋巴结同前，较大约10x7mm
    (IM100）、8x6mm （IM95）。甲状腺、双侧腮腺及颌下腺未见明显异
    常。 鼻咽及口咽、喉咽软组织影无增厚及异常强化，咽旁间隙清楚。双侧
    上颌窦粘膜增厚较前减轻。扫描范围内未见明显骨质破坏灶。

  7. 检查所见：
    对比2025-02-17胸部CT： 食管胸中下段管壁不均匀异常增厚同前，较厚部位约8mm (IM33），外膜模糊，同胸主动脉接触面小于90度，近端食管无扩张；余食管弥漫稍增厚同前，强化均匀。No.104、106、107、
    109、G3多发淋巴结同前，短径小于10mm。左肺新见多发结节（IM31 44、52等），较大约14x10mm（IM52）。双肺气肿，肺大疱同前。双肺纵隔旁斑片模糊影同前。双侧胸膜局限性增厚同前，未见胸水征象。扫及胸廓诸骨未见明确破坏征象。

  8. 临床诊断：食管癌
    症状：患者3前无明显诱因出现进食哽咽感，进行性加重，外院2022-10-19胃镜示食管距门齿30-37cm溃疡型肿物，活检病理示鳞
    状细胞癌；2022-11-2开始行白蛋白紫杉醇+铂类药+卡瑞利珠*2治疗；2022-12-22行第3周期白蛋白紫杉醇+顺铂+信迪利单抗治疗。2022-12-22评效，我院胸外科就诊考虑肿瘤与主动脉关系密切不建议手术。咨询放射治疗。目前患者乏力明显，恶心、呕吐。2023-01-10 患者今日开始放疗，具体：GTV，食管原发灶+右锁骨上、4区、8区转
    检查所见:
    与2025-02-20腹部CT比较：肝脏密度较前稍高。肝实质内未见明显异常密度及异常强化灶。胆囊、脾、胰腺、双肾及双侧肾上腺未见异常。腹腔及腹膜后未见肿大淋巴结。未见腹水征象。扫描所及诸骨未见骨质破坏灶。左肺下叶新发结节影，请结合胸部相关检查

  9. https://x.com/aigclink/status/1943833422742663313?t=BrNamENeua0JNPT-T1KuaQ&s=35
    X (formerly Twitter)
    AIGCLINK (@aigclink) on X
    阿里开源了一款医疗多模态LLM：灵枢，在多数多模态问答和报告生成任务上优于GPT-4.1、Claude Sonnet 4

    能理解处理医学图像和文本数据，进行复杂推理

    支持X光、CT、MRI、显微镜、超声、组织病理学、皮肤镜、眼底、OCT、数码摄影、内窥镜、PET12种医学影像

    2个版本：Lingshu-7B、Lingshu-32B