aws EKS集群pvc存储扩容

1、helm部署的postgresql服务出现了硬盘空间不足的日志,导致服务起不来

handlebars 复制代码
postgresql 07:31:50.95 INFO  ==> Initializing PostgreSQL database...
postgresql 07:31:50.96 INFO  ==> pg_hba.conf file not detected. Generating it...
postgresql 07:31:50.97 INFO  ==> Generating local authentication configuration
postgresql 07:31:50.98 INFO  ==> Deploying PostgreSQL with persisted data...
postgresql 07:31:50.99 INFO  ==> Configuring replication parameters
postgresql 07:31:51.01 INFO  ==> Configuring fsync
postgresql 07:31:51.02 INFO  ==> Configuring synchronous_replication
postgresql 07:31:51.05 INFO  ==> Loading custom scripts...
postgresql 07:31:51.05 INFO  ==> Enabling remote connections
postgresql 07:31:51.06 INFO  ==> ** PostgreSQL setup finished! **
postgresql 07:31:51.07 INFO  ==> ** Starting PostgreSQL **
2026-04-30 07:31:51.082 GMT [1] LOG:  pgaudit extension initialized
2026-04-30 07:31:51.082 GMT [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2026-04-30 07:31:51.082 GMT [1] LOG:  listening on IPv6 address "::", port 5432
2026-04-30 07:31:51.087 GMT [1] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"
2026-04-30 07:31:51.101 GMT [94] LOG:  database system was interrupted while in recovery at 2026-04-30 07:31:46 GMT
2026-04-30 07:31:51.101 GMT [94] HINT:  This probably means that some data is corrupted and you will have to use the last backup for recovery.
2026-04-30 07:31:51.138 GMT [94] LOG:  database system was not properly shut down; automatic recovery in progress
2026-04-30 07:31:51.142 GMT [94] LOG:  redo starts at A8/110C68C8
2026-04-30 07:31:51.187 GMT [94] LOG:  redo done at A8/14FFF970
2026-04-30 07:31:51.187 GMT [94] LOG:  last completed transaction was at log time 2026-01-08 03:08:35.382836+00
2026-04-30 07:31:51.190 GMT [94] PANIC:  could not write to file "pg_wal/xlogtemp.94": No space left on device
2026-04-30 07:31:54.323 GMT [1] LOG:  startup process (PID 94) was terminated by signal 6: Aborted
2026-04-30 07:31:54.323 GMT [1] LOG:  aborting startup due to startup process failure
2026-04-30 07:31:54.325 GMT [1] LOG:  database system is shut down

2、本想通过kuboard控制台操作,发现控制台没有权限

3、通过kubectl命令行直接操作

handlebars 复制代码
root@devops-dev:~/openclaw-platform# kubectl patch pvc data-postgre-0 -n resources -p '{"spec":{"resources":{"requests":{"storage":"200Gi"}}}}'
persistentvolumeclaim/data-postgre-0 patched

4、回到控制台查看是否扩容成功

相关推荐
A小辣椒12 天前
AWS Clould Support Engineer就职面试题
aws
亚林瓜子14 天前
AWS WAF中如何放行某个触发了托管规则的接口
aws·waf
java_cj15 天前
从kubectl学Visitor模式:如何优雅处理多态数据结构的遍历
云原生·golang·k8s·访问者模式
悠悠1213816 天前
AWS DevOps Agent 体验一周后,我决定把 oncall 手机调成静音了
云计算·aws·devops
yyuuuzz16 天前
独立站运营的几个技术层面常见问题
大数据·运维·服务器·网络·数据库·aws
yyuuuzz16 天前
游戏云服务器推荐的技术选择思路
大数据·运维·服务器·游戏·云计算·aws
java_cj16 天前
从kubectl源码学Cobra:打造专业级Go命令行工具的完整实践
运维·开发语言·后端·云原生·golang·kubernetes·k8s
逻极17 天前
Kubernetes 从入门到精通:云原生容器编排
kubernetes·k8s·服务发现·容器编排
kernelcraft18 天前
Boto3:Python 操作 AWS 的官方 SDK
开发语言·python·其他·aws
阿洛学长18 天前
Kubernetes超详细教程,从零开始学习k8s,从入门到实战
k8s·ks