顾总他天天把我按在墙上亲手机阅读_现代言情 - 得间...

2019

行动/

连忙播放收藏

《顾总他天天把我按在墙上亲手机阅读_现代言情 - 得间...》剧情简介：有场戏他对着病床上的父亲说等我公司上市就接你去治病弹幕都在刷别学他画饼嘶顾总他天天把我按在墙上亲手机阅读_现代言情 - 得间...李奶奶慰藉丑姑说道：孩子别怕一定能找到你弟弟的他一定会没事的

《顾总他天天把我按在墙上亲手机阅读_现代言情 - 得间...》视频说明：速速救治李弘浩面临江丽的乞求面临林海乔的生死攸关韩娜陷入了亘古未有的逆境Apache Pulsar学习条记14: 使用Helm在Kubernetes集群中安排Pulsar原创2021-12-31 18:22·架构小白时间过得较量久了在最先今天的学习之前先回首一下前面已经学习的13节的内容0.阶段温习Pulsar是一个支持多租户的、高性能的、漫衍式的Pub-Sub新闻系统相识Pulsar的架构Pulsar提供了一个比Cluster更高级别的笼统Instance一个Pulsar Instance由多个Pulsar Cluster组成一个Instance中的Cluster之间可以相互跨地区复制数据单个Pulsar集群由以下部分组成:Pulsar Proxy: 是无状态的Proxy作为集群的智能路由层是认真Pulsar客户端与Pulsar集群交互的统一网关Pulsar Brokers: 也是无状态的是集群的服务层Proxy会将客户端的会见请求转发到准确的Broker上Broker作为服务层与Pulsar的存储层举行交互Bookies: 一个集群有多个Bookie节点(组成Bookeeper集群)认真新闻的长期化存储Zookeeper: 用于集群级别的设置和协调并存储Pulsar集群的所有元数据以docker容器运行单机Pulsar学习使用下令行工具pulsar-admin建设tenant、namespace、topic相识Pulsar Admin REST APItenant、namespace、topic的基本看法Pulsar基于租户、命名空间、主题的逻辑条理结构支持多租户分区Topic的看法Topic URL名堂长期化Topic和非长期化Topic的看法生产者和消耗者、订阅和订阅模式Pulsar支持: exclusive(独吞), failover(故障转移/灾备), shared(共享), key-shared(基于key的共享模式) 4中订阅模式使用下令行工具pulsar-client举行生产者和消耗者测试使用Pulsar Java客户端库建设生产者、消耗者、Reader消耗者端可以使用"同步吸收新闻", "异步吸收新闻", "MessageListener吸收" 3种模式其中MessageListener自带线程池建设消耗者时可以设置消耗者的批量吸收战略多主题订阅: 设置单个消耗者订阅多个主题消耗异常处置惩罚可以使用"无限重试", "捕获并忽略异常", "死信主题（Dead Letter Topic)"三种方法使用新闻Reader可以由用户自己手动在Topic中定位读取想要读取的新闻使用Pulsar Go客户端库消耗者端支持consumer.Receive()和consumer.Chan()两种方法消耗新闻前者对channel关闭和context cancel的情形做了封装后者要我们自己处置惩罚和channel的交互但也提供了最大的无邪性多主题订阅死信战略和死信主题使用新闻Reader使用Pulsar Schema管理新闻数据的类型清静性Web图形化管理工具Pulsar Manager延迟新闻投递特征指定多长时间后投递deliverAfter指定在未来某个时间点投递deliverAt分区Topic和路由模式认证和授权开启JWT身份认证授权和权限管理前面的学习一直是基于以docker容器启动的单机Pulsar今天将学习使用Helm在Kubernetes集群中安排Pulsar集群1.情形准备这里使用的Kubernetes集群的版本是1.22.4Helm的版本是3.7.11.1 Pulsar集群组件和K8S Node节点妄想下面做一下Pulsar集群各个组件安排节点的妄想使用Pulsar官方的Helm Chart安排时可选择安排各个组件在后边的设置中将禁用监控相关的组件(promethues, grafana等)我们这里选择以后实验使用外部的全局Prometheus实现对Pulsar集群的监控本节选择安排的集群组件如下:proxy: 无状态, 但pulsar的helm chart使用StatefulSet安排broker: 无状态, 但pulsar的helm chart使用StatefulSet安排bookie: 有状态, pulsar的helm chart使用StatefulSet安排zookeeper: 有状态, pulsar的helm chart使用StatefulSet安排recovery: 无状态, 但pulsar的helm chart使用StatefulSet安排toolset: 无状态, 但pulsar的helm chart使用StatefulSet安排pulsar-manager: 无状态, pulsar的helm chart使用Deployment安排注重, pulsar-managers虽然是无状态的但由于它需要使用PostgreSQL数据库pulsar-managers的docker镜像中内置一个PostgreSQL, 这个我们在后边的设置中将改为使用集群外部的PostgreSQL下面说一下以上各个组件的安排节点选择关于proxy, broker, recovery, toolset, pulsar-manager这5个无状态组件可以让k8s将其调理到恣意节点上关于bookie, zookeeper这2个有状态组件需要我们凭证其存储卷的类型将其妄想到合适的k8s节点我们在线上情形关于有状态服务的安排在存储卷的选择上为了更好的性能一样平常都是选择Local Persistent Volumes 在因此若是你在计齐整个线上版本的Pulsar集群安排的话关于bookie和zookeeper一定需要单独的自力的k8s节点并使用这些节点上建设的Local PV 例如一个线上生产可用的Pulsar集群可能妄想如下:pulsar zookeeper集群至少需要3个自力的k8s节点, 在这些节点上建设zookeeper的local pvpulsar bookeeper集群(bookie节点组成)凭证妄想的容量需要N个自力的k8s节点, 在这些节点上建设bookie的local pv若是后续需要扩容增添bookie节点时只需要有新的建设好local pv的k8s节点并对bookie的StatefulSet扩容即可pulsar proxy, broker等无状态服务只需要有足够的数目的k8s节点并在需要时按需扩容即可因本文这里用于实验的k8s集群资源有限以是只管将上面各组件在3个k8s节点上混部将一个用于测试情形的的Pulsar集群妄想如下:k8s节点安排pulsar组件备注node1zookeeper-0, bookie-0, broker-0, proxy-0线上情形bookie和zookeeper一定要在单独的节点上node2zookeeper-1, bookie-1, broker-1, proxy-1线上情形bookie和zookeeper一定要在单独的节点上node3zookeeper-2, bookie-2, broker-2, proxy-2线上情形bookie和zookeeper一定要在单独的节点上node1或node2或node3recovery-0, toolset-0, pulsar-manager基于上面测试情形的妄想我们将node1~node3三个节点打上Label和Taint:kubectl label node node1 node-role.kubernetes.io/pulsar=pulsarkubectl label node node2 node-role.kubernetes.io/pulsar=pulsarkubectl label node node3 node-role.kubernetes.io/pulsar=pulsarkubectl taint nodes node1 dedicated=pulsar:NoSchedulekubectl taint nodes node2 dedicated=pulsar:NoSchedulekubectl taint nodes node3 dedicated=pulsar:NoScheduleLabel node-role.kubernetes.io/pulsar=pulsar用于标记节点是专门用于运行pulsar集群组件的k8s节点Taint dedicated=pulsar:NoSchedule被打到节点上后默认设置下k8s集群中的其他不属于pulsar集群组件的pod将不会被调理到这3个节点上此后边我们将要安排的pulsar组件上将会使用Toleration设置允许dedicated=pulsar:NoSchedule的Taint注重这里只是凭证测试情形Pulsar集群的妄想做了上面的Label和Taint的设置若是是生产情形这里的Label和Taint应该做更合理和细粒度的妄想确保实现上面生产可用Pulsar集群的Node节点妄想1.2 Pulsar集群组件容器镜像准备前面我们选摘要安排Pulsar集群的proxy, broker, bookie, zookeeper, recovery, toolset, pulsar-manager 7大组件其中proxy, broker, bookie, zookeeper, recovery, toolset的官方容器镜像都是apachepulsar/pulsar-all pulsar-manager的官方镜像是apachepulsar/pulsar-manager本文使用的pulsar官方的helm chart https://github.com/apache/pulsar-helm-chart/releasespulsar-helm-chart的版本为2.7.7该版本中pulsar的版本为2.7.4, pulsar-manager版本为v0.1.0:apachepulsar/pulsar-all:2.7.4apachepulsar/pulsar-manager:v0.1.0注重由于pulsar-manager:v0.1.0有这个ISSUE https://github.com/apache/pulsar-helm-chart/issues/133中形貌的问题以是在后边的安排将镜像pulsar-manager:v0.1.0替换成了pulsar-manager:v0.2.0为了提高效率这里将apachepulsar/pulsar-all:2.7.4和apachepulsar/pulsar-manager:v0.2.0这两个镜像转存到了k8s集群所使用的私有镜像客栈中例如:harbor.example.com/library/apachepulsar/pulsar-all:2.7.4harbor.example.com/library/apachepulsar/pulsar-manager:v0.2.01.3 建设JWT认证所需的K8S Secret这里安排的Pulsar集群需要在清静上开通JWT认证凭证前面学习的内容JWT支持通过两种差别的秘钥天生和验证Token:对称秘钥：使用单个Secret key来天生和验证Token非对称秘钥：包括由私钥和公钥组成的一对密钥使用Private key天生Token使用Public key验证Token推荐使用非对称密钥的方法需要先天生密钥对再用秘钥天生token由于Pulsar被安排在K8S集群中在K8S集群中存储这些秘钥和Token的最好的方法是使用K8S的Secretpulsar-helm-chart专门提供了一个prepare_helm_release.sh剧本可以用来天生这些Secret下面我们将pulsar-helm-chart的源码clone到K8S的控制节点上(kubectl和helm可用的节点):git clone -b pulsar-2.7.7 --depth 1 https://github.com/apache/pulsar-helm-chart.gitcd pulsar-helm-chart/执行下面的下令天生秘钥对和Token的Secret的Manifest:./scripts/pulsar/prepare_helm_release.sh \ -n pulsar \ -k pulsar \ -l上面的下令中:-n指定的天生Secret Manifest中装置的命名空间这里我是将其安排到K8S中的pulsar namespace中以是指定为pulsar虽然也可以指定安排到其他的namespace中-k指定的是使用helm安排时的helm release名称这里指定为pulsar-l指定只将天生的内容输出抵达外地而不会自动安排到K8S中较量喜欢这种手动的方法由于一切较量可控注重这个剧本尚有一个-s,--symmetric参数若是给这个参数的话JWT认证将使用对称秘钥的方法这里没有给这个参数就使用非对称秘钥的方法执行上面的剧本会输出以下内容:generate the token keys for the pulsar cluster---The private key and public key are generated to ... successfully.apiVersion: v1data: PRIVATEKEY: <...> PUBLICKEY: <...>kind: Secretmetadata: creationTimestamp: null name: pulsar-token-asymmetric-key namespace: pulsargenerate the tokens for the super-users: proxy-admin,broker-admin,admingenerate the token for proxy-admin---pulsar-token-asymmetric-keyapiVersion: v1data: TOKEN: <...> TYPE: YXN5bW1ldHJpYw==kind: Secretmetadata: creationTimestamp: null name: pulsar-token-proxy-admin namespace: pulsargenerate the token for broker-admin---pulsar-token-asymmetric-keyapiVersion: v1data: TOKEN: <...> TYPE: YXN5bW1ldHJpYw==kind: Secretmetadata: creationTimestamp: null name: pulsar-token-broker-admin namespace: pulsargenerate the token for admin---pulsar-token-asymmetric-keyapiVersion: v1data: TOKEN: <...> TYPE: YXN5bW1ldHJpYw==kind: Secretmetadata: creationTimestamp: null name: pulsar-token-admin namespace: pulsar-------------------------------------The jwt token secret keys are generated under: - 'pulsar-token-asymmetric-key'The jwt tokens for superusers are generated and stored as below: - 'proxy-admin':secret('pulsar-token-proxy-admin') - 'broker-admin':secret('pulsar-token-broker-admin') - 'admin':secret('pulsar-token-admin')从输出可以看出该剧本天生了4个K8S Secret的Manifest:pulsar-token-asymmetric-key这个Secret中是用于天生Token和验证Token的私钥和公钥pulsar-token-proxy-admin这个Secret中是用于proxy的超等用户角色Tokenpulsar-token-broker-admin这个Secret中是用于broker的超等用户角色Tokenpulsar-token-admin这个Secret中是用于管理客户端的超等用户角色Token接下来手动将这4个Secret使用kubectl apply建设到K8S的pulsar命名空间中建设完成后可以使用kubectl找到它们:kubectl get secret -n pulsar | grep pulsar-tokenpulsar-token-admin Opaque 2 5mpulsar-token-asymmetric-key Opaque 2 5mpulsar-token-broker-admin Opaque 2 5mpulsar-token-proxy-admin Opaque 2 5m1.4 建设Zookeeper和Bookie的Local PV凭证安排Pulsar的K8S节点的妄想下面需要为zookeeper, bookie所在的节点在K8S上建设Local Persistent Volume注重每个zookeeper节点需要一个data的local volume每个bookie节点需要journal和ledgers共两个local volume在建设Local PV之前需要确认一下k8s中保存StorageClasslocal-storage若是没有可以使用下面的manifest建设apiVersion: storage.k8s.io/v1kind: StorageClassmetadata: name: local-storageprovisioner: kubernetes.io/no-provisionervolumeBindingMode: WaitForFirstConsumerreclaimPolicy: Retain注重现在的K8S中不在直接提供local volume的provisioner这里也没有使用provisioner因以后续对local volume的建设和管理都是需要K8S集群管理员的手动举行也是说现在Kubernetes焦点中不包括对对外地卷举行动态发放和管理的provisioner若是想要体验动态发放和管理的功效可以试一下由Rancher提供的Local Path Provisioner我这里依然使用手动管理的方法即通过手动在K8S节点上建设Local Volume手动绑定Local Volume与Pulsar Zookeeper和Bookie的PVC(PersistentVolumeClaim)之间的关系下面先手动在node1, node2, node3上建设local volume对应的数据目录:mkdir -p /home/puslar/data/zookeeper-datamkdir -p /home/puslar/data/bookie-data/ledgersmkdir -p /home/puslar/data/bookie-data/journalzookeeper data的local pv的manifest如下:---apiVersion: v1kind: PersistentVolumemetadata: name: pulsar-zookeeper-data-pulsar-zookeeper-0spec: capacity: storage: 20Gi accessModes: - ReadWriteOnce persistentVolumeReclaimPolicy: Retain storageClassName: local-storage local: path: /home/puslar/data/zookeeper-data claimRef: name: pulsar-zookeeper-data-pulsar-zookeeper-0 namespace: pulsar nodeAffinity: required: nodeSelectorTerms: - matchExpressions: - key: kubernetes.io/hostname operator: In values: - node1---apiVersion: v1kind: PersistentVolumemetadata: name: pulsar-zookeeper-data-pulsar-zookeeper-1spec: capacity: storage: 20Gi accessModes: - ReadWriteOnce persistentVolumeReclaimPolicy: Retain storageClassName: local-storage local: path: /home/puslar/data/zookeeper-data claimRef: name: pulsar-zookeeper-data-pulsar-zookeeper-1 namespace: pulsar nodeAffinity: required: nodeSelectorTerms: - matchExpressions: - key: kubernetes.io/hostname operator: In values: - node2---apiVersion: v1kind: PersistentVolumemetadata: name: pulsar-zookeeper-data-pulsar-zookeeper-2spec: capacity: storage: 20Gi accessModes: - ReadWriteOnce persistentVolumeReclaimPolicy: Retain storageClassName: local-storage local: path: /home/puslar/data/zookeeper-data claimRef: name: pulsar-zookeeper-data-pulsar-zookeeper-2 namespace: pulsar nodeAffinity: required: nodeSelectorTerms: - matchExpressions: - key: kubernetes.io/hostname operator: In values: - node3上面的manifest仍中将3个Local PV通过nodeAffinity建设并关联到到node1~node3上同时使用claimRef将这3个Local PV与即将在K8S集群中安排的zookeeper SatefulSet中的PVC绑定使用kubectl apply建设上面的manifestbookie ledgers和journal的local pv的manifest如下:---apiVersion: v1kind: PersistentVolumemetadata: name: pulsar-bookie-ledgers-pulsar-bookie-0spec: capacity: storage: 50Gi accessModes: - ReadWriteOnce persistentVolumeReclaimPolicy: Retain storageClassName: local-storage local: path: /home/puslar/data/bookie-data/ledgers claimRef: name: pulsar-bookie-ledgers-pulsar-bookie-0 namespace: pulsar nodeAffinity: required: nodeSelectorTerms: - matchExpressions: - key: kubernetes.io/hostname operator: In values: - node1---apiVersion: v1kind: PersistentVolumemetadata: name: pulsar-bookie-journal-pulsar-bookie-0spec: capacity: storage: 50Gi accessModes: - ReadWriteOnce persistentVolumeReclaimPolicy: Retain storageClassName: local-storage local: path: /home/puslar/data/bookie-data/journal claimRef: name: pulsar-bookie-journal-pulsar-bookie-0 namespace: pulsar nodeAffinity: required: nodeSelectorTerms: - matchExpressions: - key: kubernetes.io/hostname operator: In values: - node1---apiVersion: v1kind: PersistentVolumemetadata: name: pulsar-bookie-ledgers-pulsar-bookie-1spec: capacity: storage: 50Gi accessModes: - ReadWriteOnce persistentVolumeReclaimPolicy: Retain storageClassName: local-storage local: path: /home/puslar/data/bookie-data/ledgers claimRef: name: pulsar-bookie-ledgers-pulsar-bookie-1 namespace: pulsar nodeAffinity: required: nodeSelectorTerms: - matchExpressions: - key: kubernetes.io/hostname operator: In values: - node2---apiVersion: v1kind: PersistentVolumemetadata: name: pulsar-bookie-journal-pulsar-bookie-1spec: capacity: storage: 50Gi accessModes: - ReadWriteOnce persistentVolumeReclaimPolicy: Retain storageClassName: local-storage local: path: /home/puslar/data/bookie-data/journal claimRef: name: pulsar-bookie-journal-pulsar-bookie-1 namespace: pulsar nodeAffinity: required: nodeSelectorTerms: - matchExpressions: - key: kubernetes.io/hostname operator: In values: - node2---apiVersion: v1kind: PersistentVolumemetadata: name: pulsar-bookie-ledgers-pulsar-bookie-2spec: capacity: storage: 50Gi accessModes: - ReadWriteOnce persistentVolumeReclaimPolicy: Retain storageClassName: local-storage local: path: /home/puslar/data/bookie-data/ledgers claimRef: name: pulsar-bookie-ledgers-pulsar-bookie-2 namespace: pulsar nodeAffinity: required: nodeSelectorTerms: - matchExpressions: - key: kubernetes.io/hostname operator: In values: - node3---apiVersion: v1kind: PersistentVolumemetadata: name: pulsar-bookie-journal-pulsar-bookie-2spec: capacity: storage: 50Gi accessModes: - ReadWriteOnce persistentVolumeReclaimPolicy: Retain storageClassName: local-storage local: path: /home/puslar/data/bookie-data/journal claimRef: name: pulsar-bookie-journal-pulsar-bookie-2 namespace: pulsar nodeAffinity: required: nodeSelectorTerms: - matchExpressions: - key: kubernetes.io/hostname operator: In values: - node3上面的manifest仍中将6个Local PV通过nodeAffinity建设并关联到到node1~node3上同时使用claimRef将这3个Local PV与即将在K8S集群中安排的zookeeper SatefulSet中的PVC绑定使用kubectl apply建设上面的manifest1.5 准备Pulsar Manager的PostgreSQL数据库这里准备让Pulsar Manager使用外部数据库需要提前在外部的PostgreSQL中建设好用户和数据库表结构建设数据库和用户:CREATE USER pulsar_manager WITH PASSWORD '';CREATE DATABASE pulsar_manager OWNER pulsar_manager;GRANT ALL PRIVILEGES ON DATABASE pulsar_manager to pulsar_manager;GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA pulsar_manager TO pulsar_manager;ALTER SCHEMA public OWNER to pulsar_manager;GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA public TO pulsar_manager;GRANT ALL PRIVILEGES ON ALL SEQUENCES IN SCHEMA public TO pulsar_manager;建设表结构(建表剧本可以在pulsar-manager的镜像中找到):CREATE TABLE IF NOT EXISTS environments ( name varchar(256) NOT NULL, broker varchar(1024) NOT NULL, CONSTRAINT PK_name PRIMARY KEY (name), UNIQUE (broker));CREATE TABLE IF NOT EXISTS topics_stats ( topic_stats_id BIGSERIAL PRIMARY KEY, environment varchar(255) NOT NULL, cluster varchar(255) NOT NULL, broker varchar(255) NOT NULL, tenant varchar(255) NOT NULL, namespace varchar(255) NOT NULL, bundle varchar(255) NOT NULL, persistent varchar(36) NOT NULL, topic varchar(255) NOT NULL, producer_count BIGINT, subscription_count BIGINT, msg_rate_in double precision , msg_throughput_in double precision , msg_rate_out double precision , msg_throughput_out double precision , average_msg_size double precision , storage_size double precision , time_stamp BIGINT);CREATE TABLE IF NOT EXISTS publishers_stats ( publisher_stats_id BIGSERIAL PRIMARY KEY, producer_id BIGINT, topic_stats_id BIGINT NOT NULL, producer_name varchar(255) NOT NULL, msg_rate_in double precision , msg_throughput_in double precision , average_msg_size double precision , address varchar(255), connected_since varchar(128), client_version varchar(36), metadata text, time_stamp BIGINT, CONSTRAINT fk_publishers_stats_topic_stats_id FOREIGN KEY (topic_stats_id) References topics_stats(topic_stats_id));CREATE TABLE IF NOT EXISTS replications_stats ( replication_stats_id BIGSERIAL PRIMARY KEY, topic_stats_id BIGINT NOT NULL, cluster varchar(255) NOT NULL, connected BOOLEAN, msg_rate_in double precision , msg_rate_out double precision , msg_rate_expired double precision , msg_throughput_in double precision , msg_throughput_out double precision , msg_rate_redeliver double precision , replication_backlog BIGINT, replication_delay_in_seconds BIGINT, inbound_connection varchar(255), inbound_connected_since varchar(255), outbound_connection varchar(255), outbound_connected_since varchar(255), time_stamp BIGINT, CONSTRAINT FK_replications_stats_topic_stats_id FOREIGN KEY (topic_stats_id) References topics_stats(topic_stats_id));CREATE TABLE IF NOT EXISTS subscriptions_stats ( subscription_stats_id BIGSERIAL PRIMARY KEY, topic_stats_id BIGINT NOT NULL, subscription varchar(255) NULL, msg_backlog BIGINT, msg_rate_expired double precision , msg_rate_out double precision , msg_throughput_out double precision , msg_rate_redeliver double precision , number_of_entries_since_first_not_acked_message BIGINT, total_non_contiguous_deleted_messages_range BIGINT, subscription_type varchar(16), blocked_subscription_on_unacked_msgs BOOLEAN, time_stamp BIGINT, UNIQUE (topic_stats_id, subscription), CONSTRAINT FK_subscriptions_stats_topic_stats_id FOREIGN KEY (topic_stats_id) References topics_stats(topic_stats_id));CREATE TABLE IF NOT EXISTS consumers_stats ( consumer_stats_id BIGSERIAL PRIMARY KEY, consumer varchar(255) NOT NULL, topic_stats_id BIGINT NOT NUll, replication_stats_id BIGINT, subscription_stats_id BIGINT, address varchar(255), available_permits BIGINT, connected_since varchar(255), msg_rate_out double precision , msg_throughput_out double precision , msg_rate_redeliver double precision , client_version varchar(36), time_stamp BIGINT, metadata text);CREATE TABLE IF NOT EXISTS tokens ( token_id BIGSERIAL PRIMARY KEY, role varchar(256) NOT NULL, description varchar(128), token varchar(1024) NOT NUll, UNIQUE (role));CREATE TABLE IF NOT EXISTS users ( user_id BIGSERIAL PRIMARY KEY, access_token varchar(256), name varchar(256) NOT NULL, description varchar(128), email varchar(256), phone_number varchar(48), location varchar(256), company varchar(256), expire BIGINT, password varchar(256), UNIQUE (name));CREATE TABLE IF NOT EXISTS roles ( role_id BIGSERIAL PRIMARY KEY, role_name varchar(256) NOT NULL, role_source varchar(256) NOT NULL, description varchar(128), resource_id BIGINT NOT NULL, resource_type varchar(48) NOT NULL, resource_name varchar(48) NOT NULL, resource_verbs varchar(256) NOT NULL, flag INT NOT NULL);CREATE TABLE IF NOT EXISTS tenants ( tenant_id BIGSERIAL PRIMARY KEY, tenant varchar(255) NOT NULL, admin_roles varchar(255), allowed_clusters varchar(255), environment_name varchar(255), UNIQUE(tenant));CREATE TABLE IF NOT EXISTS namespaces ( namespace_id BIGSERIAL PRIMARY KEY, tenant varchar(255) NOT NULL, namespace varchar(255) NOT NULL, UNIQUE(tenant, namespace));CREATE TABLE IF NOT EXISTS role_binding( role_binding_id BIGSERIAL PRIMARY KEY, name varchar(256) NOT NULL, description varchar(256), role_id BIGINT NOT NULL, user_id BIGINT NOT NULL);上面已经做好了安排的准备事情下面将使用Helm在K8S集群中安排Pulsar集群2.使用Helm在K8S中安排Pulsar从https://github.com/apache/pulsar-helm-chart/releases下载pulsar helm chart 2.7.7到K8S的控制节点上(kubectl和helm可用)https://github.com/apache/pulsar-helm-chart/releases/download/pulsar-2.7.7/pulsar-2.7.7.tgz2.1 定制编写helm chart的values.yaml定制编写helm chart的values.yaml文件如下, 定制的内容较量多详细见下面文件的注释:auth: authentication: enabled: true # 开启jwt认证 provider: "jwt" jwt: usingSecretKey: false # jwt认证使用非对称秘钥对 authorization: enabled: true # 开启授权 superUsers: # broker to broker communication broker: "broker-admin" # proxy to broker communication proxy: "proxy-admin" # pulsar-admin client to broker/proxy communication client: "admin"components: # 启用的组件 autorecovery: true bookkeeper: true broker: true functions: true proxy: true pulsar_manager: true toolset: true zookeeper: truemonitoring: # 关闭监控组件, 后续实验使用外部Prometheus对pulsar集群举行监控 grafana: false prometheus: false node_exporter: falsevolumes: local_storage: true # 数据卷使用local storageproxy: # proxy的设置(这里是测试情形, 将proxy也调理到node1或node2或node3) nodeSelector: node-role.kubernetes.io/pulsar: pulsar tolerations: - key: "dedicated" operator: "Equal" value: "pulsar" effect: "NoSchedule" configData: PULSAR_PREFIX_authenticateMetricsEndpoint: "false"broker: # broker的设置(这里是测试情形, 将proxy也调理到node1或node2或node3) nodeSelector: node-role.kubernetes.io/pulsar: pulsar tolerations: - key: "dedicated" operator: "Equal" value: "pulsar" effect: "NoSchedule" zookeeper: # broker的设置 replicaCount: 3 tolerations: - key: "dedicated" operator: "Equal" value: "pulsar" effect: "NoSchedule" volumes: data: # 设置使用local pv, 需要与前面手动建设的local pv信息一致 local_storage: true size: 20Gibookkeeper: # bookkeeper的设置 replicaCount: 3 tolerations: - key: "dedicated" operator: "Equal" value: "pulsar" effect: "NoSchedule" volumes: journal: # 设置使用local pv, 需要与前面手动建设的local pv信息一致 local_storage: true size: 50Gi ledgers: # 设置使用local pv, 需要与前面手动建设的local pv信息一致 local_storage: true size: 50Gipulsar_manager: # pulsar_manager的设置(这里是测试情形, 将pulsar_manager也调理到node1或node2或node3) replicaCount: 1 admin: # 文档中形貌这里是pulsar manager web界面登任命户密码但现实受骗使用外部PostgreSQL数据库时这里需要指定PostgreSQL的数据库和密码不知道是否是pulsar-helm-chart 2.7.7的问题 user: pulsar_manager password: 05aM3Braz_M4RWpn configData: DRIVER_CLASS_NAME: org.postgresql.Driver URL: jdbc:postgresql://:5432/pulsar_manager # 文档中形貌这里PostgreSQL数据库的密码但现实上这里不可指定USERNAME和PASSWORD, 不知道是否是pulsar-helm-chart 2.7.7的问题 # USERNAME: pulsar_manager # PASSWORD: 05aM3Braz_M4RWpn LOG_LEVEL: INFO ## 开启JWT认证后, 这里需要指定pulsar-token-admin这个Secret中的JWT Token JWT_TOKEN: autorecovery: # autorecovery的设置(这里是测试情形, 将autorecovery也调理到node1或node2或node3) replicaCount: 1 nodeSelector: node-role.kubernetes.io/pulsar: pulsar tolerations: - key: "dedicated" operator: "Equal" value: "pulsar" effect: "NoSchedule"toolset: # toolset的设置(这里是测试情形, 将toolset也调理到node1或node2或node3) replicaCount: 1 nodeSelector: node-role.kubernetes.io/pulsar: pulsar tolerations: - key: "dedicated" operator: "Equal" value: "pulsar" effect: "NoSchedule"images: # 对个组件使用私有镜像客栈的设置 imagePullSecrets: - regsecret # 私有镜像客栈的image pull secret, 需要提前在k8s命名空间中建设 autorecovery: repository: harbor.example.com/library/apachepulsar/pulsar-all tag: 2.7.4 bookie: repository: harbor.example.com/library/apachepulsar/pulsar-all tag: 2.7.4 broker: repository: harbor.example.com/library/apachepulsar/pulsar-all tag: 2.7.4 functions: repository: harbor.example.com/library/apachepulsar/pulsar-all tag: 2.7.4 proxy: repository: harbor.example.com/library/apachepulsar/pulsar-all tag: 2.7.4 pulsar_manager: repository: harbor.example.com/library/apachepulsar/pulsar-manager tag: v0.2.0 zookeeper: repository: harbor.example.com/library/apachepulsar/pulsar-all tag: 2.7.4pulsar_metadata: component: pulsar-init image: # the image used for running `pulsar-cluster-initialize` job repository: harbor.example.com/library/apachepulsar/pulsar-all tag: 2.7.4由于目今在pulsar-helm-chart 2.7.7 中似乎不支持为pulsar-init设置私有客栈的imagePullSecret以是下面为pulsar namespace中的default servcieaccount 添加上imagePullSecretkubectl patch serviceaccount default -p '{"imagePullSecrets": [{"name": "regsecret"}]}' -n pulsar2.2 使用helm install装置pulsar定制完value.yaml之后使用下面的下令向K8S集群安排pulsarhelm install \ --values values.yaml \ --set initialize=true \ --namespace pulsar \ pulsar pulsar-2.7.7.tgz装置完成后使用下面的下令审查一下两个初始化job pulsar-pulsar-init和pulsar-bookie-init的pod状态为Complete:kubectl get pod -n pulsar | grep initpulsar-bookie-init--1-h65bp 0/1 Completed 0 5m14spulsar-pulsar-init--1-t4thq 0/1 Completed 0 5m5s使用下面的下令审查一下pulsar集群各个组件的Pod状态所有都为Running:kubectl get pod -n pulsar -l cluster=pulsar -o wideNAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATESpulsar-bookie-0 1/1 Running 0 14m 10.244.226.91 node1 pulsar-bookie-1 1/1 Running 0 14m 10.244.63.90 node2 pulsar-bookie-2 1/1 Running 0 14m 10.244.46.92 node3 pulsar-broker-0 1/1 Running 0 14m 10.244.226.90 node1 pulsar-broker-1 1/1 Running 0 14m 10.244.63.89 node2 pulsar-broker-2 1/1 Running 0 14m 10.244.46.90 node3 pulsar-proxy-0 1/1 Running 0 14m 10.244.226.93 node1 pulsar-proxy-1 1/1 Running 0 14m 10.244.63.91 node2 pulsar-proxy-2 1/1 Running 0 14m 10.244.46.93 node3 pulsar-pulsar-manager-7b98666cff-5626f 1/1 Running 0 14m 10.244.63.88 node2 pulsar-recovery-0 1/1 Running 0 14m 10.244.46.89 node3 pulsar-toolset-0 1/1 Running 0 14m 10.244.46.91 node3 pulsar-zookeeper-0 1/1 Running 0 14m 10.244.226.92 node1 pulsar-zookeeper-1 1/1 Running 0 14m 10.244.63.92 node2 pulsar-zookeeper-2 1/1 Running 0 13m 10.244.46.94 node3 若是后边调解了values.yaml需要更新安排时使用下面的下令:helm upgrade pulsar pulsar-2.7.7.tgz \ --namespace pulsar \ -f values.yaml2.3 在toolset pod中测试建设tenant, namespace和topictoolset pod中包括了种种管理和测试pulsar的下令行工具例如pulsar-admin, pulsar-client等下面进入toolset pod中使用pulsar-admin下令行工具测试一下tenant, namespace和topic的建设进一步确认pulsar集群事情正常kubectl exec -it -n pulsar pulsar-toolset-0 -- /bin/bashbin/pulsar-admin tenants create test-tenantbin/pulsar-admin tenants list"public""pulsar""test-tenant"bin/pulsar-admin namespaces create test-tenant/test-nsbin/pulsar-admin namespaces list test-tenant"test-tenant/test-ns"bin/pulsar-admin topics create-partitioned-topic test-tenant/test-ns/test-topic -p 3bin/pulsar-admin topics list-partitioned-topics test-tenant/test-ns"persistent://test-tenant/test-ns/test-topic"2.4 建设pulsar-manager的管理员用户并登录审查下面测试一下pulsar manager是否可以使用前面使用helm chart安排的pulsar集群在k8s中建设了下面7个Servicekubectl get svc -l app=pulsar -n pulsarNAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGEpulsar-bookie ClusterIP None 3181/TCP,8000/TCP 40mpulsar-broker ClusterIP None 8080/TCP,6650/TCP 40mpulsar-proxy LoadBalancer 10.104.105.137 80:31970/TCP,6650:32631/TCP 40mpulsar-pulsar-manager LoadBalancer 10.110.207.9 9527:32764/TCP 40mpulsar-recovery ClusterIP None 8000/TCP 40mpulsar-toolset ClusterIP None 40mpulsar-zookeeper ClusterIP None 8000/TCP,2888/TCP,3888/TCP,2181/TCP 40m从上面下令的输出可以看出bookie, broker, recovery, toolset, zookeeper这5个Service的类型都是ClusterIP的并且cluser-ip为None都是Headless的Service由于它们只需要在k8s集群内部使用pulsar-proxy和pulsar-pulsar-manager为LoadBalancer类型并且都设置了NodePort提供了从K8S集群外部会见的能力从集群外部会见pulsar-manager的地址是http://node1:32764第一次会见pulsar manager之前需要为其建设一个管理用户:CSRF_TOKEN=$(curl http://node1:32764/pulsar-manager/csrf-token)curl \ -H 'X-XSRF-TOKEN: $CSRF_TOKEN' \ -H 'Cookie: XSRF-TOKEN=$CSRF_TOKEN;' \ -H "Content-Type: application/json" \ -X PUT http://node1:32764/pulsar-manager/users/superuser \ -d '{"name": "admin", "password": "pulsar", "description": "test", "email": "username@test.org"}'上面的下令为pulsar-manager建设用户名为admin, 密码为pulsar的管理用户使用该用户就可以登录pulsar manager备注, 在线上使用时只管阻止以NodePort袒露服务这里的pulsar-manager的Service可以修改为CluserIP类型并关闭NodePort同时建设Ingress以Ingress+域名的形式袒露出来看了一下pulsar-helm-chart也是支持的只是现在pulsar-helm-chart 2.7.7中建设Ingress时使用的是apiVersion: extensions/v1beta1 API这个API从k8s 1.19被标记为放弃在k8s 1.22已被移除以是要直接是使用pulsar-helm-chart建设Ingress的话需要期待pulsar-helm-chart的更新参考https://github.com/apache/pulsar-helm-charthttps://pulsar.apache.org/docs/zh-CN/kubernetes-helm/https://github.com/apache/pulsar-helm-chart/issues/133https://github.com/rancher/local-path-provisionerhttps://kubernetes.io/zh/docs/tasks/configure-pod-container/configure-service-account/

对了九霄天宫你闯的怎么样血魔刀圣随即有些期待地问道丁奉看着钱没少花一点希望没有愁的都睡不着觉怎么办才华把荒山酿成茶山呢他在床上翻来覆去想出了一条毒计

它全身都由石块组成充满着浓郁的土道道痕龙身厚重龙牙宛若石林古拙大气威勐震撼国庆节济南14个婚姻挂号处为爱加班值班表宣布

腾博tengbo9885官网

顾总他天天把我按在墙上亲手机阅读_现代言情 - 得间...

选集播放排序

相关推荐TUIJIAN

正在热映

选集播放
排序