Auto-sync: update nexus workspace
This commit is contained in:
53
wiki/entities/Amazon-EKS.md
Normal file
53
wiki/entities/Amazon-EKS.md
Normal file
@@ -0,0 +1,53 @@
|
||||
---
|
||||
title: "Amazon EKS"
|
||||
type: entity
|
||||
tags:
|
||||
- AWS
|
||||
- Kubernetes
|
||||
- EKS
|
||||
- Container-Orchestration
|
||||
- SaaS
|
||||
sources:
|
||||
- ctp-topic-39-implementing-eks-in-the-aws-lab-landing-zone
|
||||
- ctp-topic-70-eks-deployment-using-iac
|
||||
- ctp-topic-59-achieving-reliability-with-amazon-eks
|
||||
- ctp-topic-64-scaling-out-with-amazon-eks
|
||||
last_updated: 2026-04-28
|
||||
---
|
||||
|
||||
## Overview
|
||||
Amazon Elastic Kubernetes Service (EKS) 是 AWS 提供的托管 Kubernetes 服务,负责 Kubernetes 控制平面的可用性和伸缩性,用户只需管理工作节点(数据平面)。
|
||||
|
||||
## Aliases
|
||||
- EKS
|
||||
- Amazon Elastic Kubernetes Service
|
||||
- Amazon EKS
|
||||
|
||||
## Key Characteristics
|
||||
- 完全托管的控制平面(Control Plane)
|
||||
- 与 AWS 服务深度集成(IAM、VPC、ELB、EBS、S3 等)
|
||||
- 支持 Fargate(无服务器计算引擎)和自管理/托管节点组
|
||||
- IAM RBAC 最小权限模型
|
||||
- 零停机滚动更新
|
||||
|
||||
## Architecture Components
|
||||
- **控制平面**:跨 3 AZ 部署,由 AWS 自动管理 etcd 和 API Server
|
||||
- **数据平面**:Worker Nodes(EC2、自管理或托管节点组)
|
||||
- **Pod 网络**:VPC CNI(默认)或自定义网络模式
|
||||
- **Ingress**:AWS ALB Ingress Controller
|
||||
- **存储**:EBS CSI Driver
|
||||
|
||||
## EKS Custom Networking
|
||||
EKS 支持自定义网络配置,允许绕过 VPC CNI 的默认行为,控制 Pod IP 分配。在受限 IP 地址池的环境中(如 AWS Lab Landing Zone),通过自定义网络标志启用独立子网的 IP 分配。
|
||||
|
||||
## Key Sources
|
||||
- [[ctp-topic-39-implementing-eks-in-the-aws-lab-landing-zone]]:在受限 Lab Landing Zone 中的 EKS 实施,解决 IP 地址池不足问题
|
||||
- [[ctp-topic-70-eks-deployment-using-iac]]:通过 Terraform IaC 部署 EKS 的完整方法论
|
||||
- [[ctp-topic-59-achieving-reliability-with-amazon-eks]]:EKS 可靠性最佳实践
|
||||
- [[ctp-topic-64-scaling-out-with-amazon-eks]]:EKS 自动扩缩容策略
|
||||
|
||||
## Related Entities
|
||||
- [[AWS-Landing-Zone]]:EKS 部署的底层基础设施框架
|
||||
- [[AWS]]:EKS 所属的云平台提供商
|
||||
- [[Jenkins]]:EKS 部署的 CI/CD 平台(替代 Atlantis)
|
||||
- [[TerraGrant]]:Terragrunt 模块封装
|
||||
26
wiki/entities/BrightCloud.md
Normal file
26
wiki/entities/BrightCloud.md
Normal file
@@ -0,0 +1,26 @@
|
||||
---
|
||||
title: "BrightCloud"
|
||||
type: entity
|
||||
tags:
|
||||
- OpenText
|
||||
- Threat-Intelligence
|
||||
- Security-Tools
|
||||
last_updated: 2026-04-14
|
||||
---
|
||||
|
||||
# BrightCloud
|
||||
|
||||
**Type:** Product / Security Tool | **Company:** OpenText
|
||||
|
||||
## Overview
|
||||
BrightCloud 是 OpenText 自有的威胁情报工具,作为威胁情报 feeds 的来源,整合到 OpenText 的安全运营体系中。
|
||||
|
||||
## Usage in OpenText
|
||||
- 作为威胁情报 feed 输入到 OpenText 的安全运营平台
|
||||
- 支撑月处理 2250 亿条日志的安全运营体系
|
||||
- 与检测和威胁狩猎(Threat Hunting)结合使用
|
||||
|
||||
## Connections
|
||||
- [[OpenText]]:开发公司
|
||||
- [[Threat-Intelligence]]:所属领域
|
||||
- [[Global Information Security Team (GIS)]]:使用团队
|
||||
28
wiki/entities/Ed.md
Normal file
28
wiki/entities/Ed.md
Normal file
@@ -0,0 +1,28 @@
|
||||
---
|
||||
title: "Ed"
|
||||
type: entity
|
||||
tags:
|
||||
- OpenText
|
||||
- GIS
|
||||
- Security
|
||||
last_updated: 2026-04-14
|
||||
---
|
||||
|
||||
# Ed
|
||||
|
||||
**Role:** Global Information Security Team (GIS), OpenText
|
||||
|
||||
## Overview
|
||||
Ed 是 OpenText 全球信息安全团队(GIS)的核心成员,与 Mike 共同主持了关于 GIS 安全策略的公开云学习会议。
|
||||
|
||||
## Contributions
|
||||
- 主持 GIS Security Policies 学习会议(2024年10月15日)
|
||||
- 阐述 GIS 组织架构与政策框架
|
||||
|
||||
## Aliases
|
||||
- Ed(GIS)
|
||||
|
||||
## Connections
|
||||
- [[Mike]]:同事,共同主持 GIS 学习会议
|
||||
- [[Global Information Security Team (GIS)]]:所属团队
|
||||
- [[OpenText]]:雇主
|
||||
28
wiki/entities/Mike.md
Normal file
28
wiki/entities/Mike.md
Normal file
@@ -0,0 +1,28 @@
|
||||
---
|
||||
title: "Mike"
|
||||
type: entity
|
||||
tags:
|
||||
- OpenText
|
||||
- GIS
|
||||
- Security
|
||||
last_updated: 2026-04-14
|
||||
---
|
||||
|
||||
# Mike
|
||||
|
||||
**Role:** Global Information Security Team (GIS), OpenText
|
||||
|
||||
## Overview
|
||||
Mike 是 OpenText 全球信息安全团队(GIS)的核心成员,与 Ed 共同主持了关于 GIS 安全策略的公开云学习会议。
|
||||
|
||||
## Contributions
|
||||
- 主持 GIS Security Policies 学习会议(2024年10月15日)
|
||||
- 阐述 GIS 组织架构与政策框架
|
||||
|
||||
## Aliases
|
||||
- Mike(GIS)
|
||||
|
||||
## Connections
|
||||
- [[Ed]]:同事,共同主持 GIS 学习会议
|
||||
- [[Global Information Security Team (GIS)]]:所属团队
|
||||
- [[OpenText]]:雇主
|
||||
43
wiki/entities/Octane.md
Normal file
43
wiki/entities/Octane.md
Normal file
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: "Octane"
|
||||
type: entity
|
||||
tags:
|
||||
- MicroFocus
|
||||
- SaaS
|
||||
- Kubernetes
|
||||
- EKS
|
||||
sources:
|
||||
- ctp-topic-39-implementing-eks-in-the-aws-lab-landing-zone
|
||||
- ctp-topic-14-octane-hub-on-aws-real-life-experience-moving-production-services-i
|
||||
last_updated: 2026-04-28
|
||||
---
|
||||
|
||||
## Overview
|
||||
Octane 是 Micro Focus(现 OpenText)旗下一款 SaaS 应用,以 IP 地址密集型(IP-hungry)workload 著称,是推动 EKS 在 AWS Lab Landing Zone 中实施的核心业务驱动因素。
|
||||
|
||||
## Aliases
|
||||
- Octane
|
||||
- Micro Focus Octane
|
||||
- Octane SaaS
|
||||
|
||||
## Key Characteristics
|
||||
- SaaS 模式部署
|
||||
- IP 地址密集型应用,对 IP 分配有大量需求
|
||||
- 在 AWS 环境中需要 Kubernetes 容器编排能力
|
||||
- 驱动了 OpenText/Micro Focus 团队对 EKS 自定义网络方案的探索
|
||||
|
||||
## Context
|
||||
Octane 是 CTP Topic 39 中 EKS 部署的驱动用例。标准 EKS 部署方案无法满足其 IP 需求,团队通过以下方案解决:
|
||||
- 创建独立私有子网(非主 VPC 子网)
|
||||
- 启用 EKS 模块的自定义网络配置标志
|
||||
- 在 Pod 规范中设置 `hostNetwork: true`
|
||||
|
||||
## Related Entities
|
||||
- [[Amazon-EKS]]:Octane 部署的容器编排平台
|
||||
- [[AWS-Landing-Zone]]:Octane 运行的 AWS 基础设施环境
|
||||
- [[MicroFocus]]:(历史)开发 Octane 的公司
|
||||
- [[OpenText]]:(现母公司)
|
||||
|
||||
## Related Sources
|
||||
- [[ctp-topic-39-implementing-eks-in-the-aws-lab-landing-zone]]
|
||||
- [[ctp-topic-14-octane-hub-on-aws-real-life-experience-moving-production-services-i]]
|
||||
@@ -1,24 +1,36 @@
|
||||
---
|
||||
title: "Suravpul"
|
||||
type: entity
|
||||
tags: [AWS, Solutions-Architect, EKS]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
# Suravpul
|
||||
|
||||
AWS 高级解决方案架构师(Senior Solutions Architect),专注 Amazon EKS 的可靠性、可观测性和扩缩容实践。
|
||||
|
||||
## Role
|
||||
- AWS Senior Solutions Architect
|
||||
- 主讲 CTP 云转型系列中多个 EKS 深度专题
|
||||
|
||||
## Sources
|
||||
- [[ctp-topic-59-achieving-reliability-with-amazon-eks]] — EKS 可靠性最佳实践
|
||||
- [[ctp-topic-64-scaling-out-with-amazon-eks]] — EKS 工作负载扩缩容
|
||||
- [[ctp-topic-67-cloud-native-observability-using-opentelemetry]] — EKS 云原生可观测性
|
||||
|
||||
## Connections
|
||||
- [[Amazon EKS]] — 专注领域
|
||||
- [[AWS]] — 雇主
|
||||
- [[Surav Paul]] — 同一人:ctp-topic-59 标注为 "Surav Paul",本视频标注为 "Suravpul",推断为同一 AWS 高级解决方案架构师的不同记法
|
||||
---
|
||||
title: "Suravpul"
|
||||
type: entity
|
||||
tags:
|
||||
- AWS
|
||||
- Solutions-Architect
|
||||
- EKS
|
||||
- Kubernetes
|
||||
sources:
|
||||
- ctp-topic-59-achieving-reliability-with-amazon-eks
|
||||
- ctp-topic-64-scaling-out-with-amazon-eks
|
||||
- ctp-topic-67-cloud-native-observability-using-opentelemetry
|
||||
last_updated: 2026-04-28
|
||||
---
|
||||
|
||||
## Overview
|
||||
Suravpul 是 Amazon Web Services(AWS)的高级解决方案架构师(Senior Solutions Architect),专注于 Amazon EKS(Elastic Kubernetes Service)的可靠性、可观测性和扩缩容实践。
|
||||
|
||||
## Aliases
|
||||
- Suravpul
|
||||
- Suravpul (AWS)
|
||||
|
||||
## Key Contributions
|
||||
- CTP Topic 59:EKS 可靠性深度实践(HPA、VPA、Pod Disruption Budget)
|
||||
- CTP Topic 64:EKS 工作负载扩缩容完整方法论(HPA、KEDA、Cluster Autoscaler、Karpenter、IPv6)
|
||||
- CTP Topic 67:云原生可观测性最佳实践(OpenTelemetry 集成)
|
||||
|
||||
## Role
|
||||
- **Organization**: Amazon Web Services (AWS)
|
||||
- **Title**: Senior Solutions Architect
|
||||
- **Focus Areas**: EKS reliability, observability, autoscaling, container networking
|
||||
|
||||
## Sources
|
||||
- [[ctp-topic-59-achieving-reliability-with-amazon-eks]]
|
||||
- [[ctp-topic-64-scaling-out-with-amazon-eks]]
|
||||
- [[ctp-topic-67-cloud-native-observability-using-opentelemetry]]
|
||||
|
||||
Reference in New Issue
Block a user